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

Use both minimal and maximal versions in CI #305

Open
joshlf opened this issue Sep 1, 2023 · 0 comments
Open

Use both minimal and maximal versions in CI #305

joshlf opened this issue Sep 1, 2023 · 0 comments
Labels
compatibility-nonbreaking Changes that are (likely to be) non-breaking

Comments

@joshlf
Copy link
Member

joshlf commented Sep 1, 2023

See also: #1595

By default, when Cargo is performing dependency resolution, it tries to find the maximum version of each dependency which satisfies the dependency constraints. However, this can hide issues such as accidentally depending upon a feature that was introduced after the minimum version specified by a dependency. In order to catch these errors, we should also test with Cargo's minimal-version flag. This flag is unstable, so we'll only be able to do this on the nightly toolchain, and we may have to remove it at some point if the feature breaks or is removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility-nonbreaking Changes that are (likely to be) non-breaking
Projects
None yet
Development

No branches or pull requests

1 participant