Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should compat version ranges in Project.toml be more restrictive? #308

Closed
galenlynch opened this issue Jun 10, 2019 · 1 comment
Closed

Should compat version ranges in Project.toml be more restrictive? #308

galenlynch opened this issue Jun 10, 2019 · 1 comment

Comments

@galenlynch
Copy link
Member

#306 Makes me wonder if the current compat ranges, which only set a lower bound on the versions of dependencies, are the best choice. I know some other packages also specify an upper bound, as there is no guarantee that the next major version of a dependency will not change its API in a way that will break DSP.jl.
@ararslan
Copy link
Member

ararslan commented Jan 1, 2020

Seems things are good now.

@ararslan ararslan closed this as completed Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ararslan @galenlynch