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.

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

Minimal versions #79

Merged
merged 3 commits into from Dec 16, 2021
Merged

Minimal versions #79

merged 3 commits into from Dec 16, 2021

Conversation

djc
Copy link
Contributor

@djc djc commented Dec 16, 2021

I noticed you seem to use cargo upgrade to upgrade all dependencies. However, I think forcing downstream users to use the latest versions of all of your dependencies is not a great idea. Case in point, 2 days ago futures 0.3.18 got yanked. As part of routine upgrades in #77, you forced downstream users to use 0.3.18, such that now your 0.3.2 is no longer usable if I want to stick with futures 0.3.17.

Here I used cargo update -Z minimal-versions to build a Cargo.lock with the oldest semver-compatible versions and then tried to run the tests. In order to get the tests to work I had to bump async-std to 1.5 and chrono to 0.4.1, but otherwise the tests at least work.

There were some unused value warnings, which I fixed in a separate commit.

I recommend you use cargo upgrade with the --skip-compatible option in the future for public library crates.

Copy link
Owner

@mattsse mattsse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thank you!

@mattsse mattsse merged commit 4b18a00 into mattsse:main Dec 16, 2021
@djc djc mentioned this pull request Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants