Use upper bounds for dependencies #74
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The standard practice is now to have upper bounds so that the package doesn't break when a dependency tags a breaking release. CompatHelper makes it easy to update the bounds when a new version comes out. Without these bounds, registering new versions requires manual intervention.
|
@juliangehring If that's OK with you could you tag a release? Currently Bootstrap.jl conflicts with DataFrames.jl 0.22. Ideally the package wouldn't depend on DataFrames and use the Tables.jl API instead. Shouldn't be too hard. |
|
@nalimilan Thank you! I'll tag a new release with these changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The standard practice is now to have upper bounds so that the package doesn't break when a dependency tags a breaking release.
CompatHelper makes it easy to update the bounds when a new version comes out.
Without these bounds, registering new versions requires manual intervention.
After tagging a release, will fix #72 and will fix #73.