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

fix(msrv): Put MSRV-aware resolver behind a config #13769

Merged
merged 4 commits into from
Apr 18, 2024
Merged

fix(msrv): Put MSRV-aware resolver behind a config #13769

merged 4 commits into from
Apr 18, 2024

Commits on Apr 17, 2024

  1. test(resolver): Verify some more msrv cases

    @epage
    epage committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    226b53e View commit details
    Browse the repository at this point in the history

  2. test(msrv): Prep for config to be added

    @epage
    epage committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    34afc4f View commit details
    Browse the repository at this point in the history

  3. test(msrv): Show config on stable

    @epage
    epage committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    7af4bcf View commit details
    Browse the repository at this point in the history

  4. fix(msrv): Put MSRV-aware resolver behind a config 

    This is a part of rust-lang#13540 which is a party of rust-lang#9930.

The config is `resolver.something-like-precedence` with values:
- `something-like-maximum` (default)
- `something-like-rust-version`

This is punting on the actual config schema so we can implement
`package.resolver` and `edition = "2024"` support as we want the
MSRV-aware resolver available without `cargo_features`.
    @epage
    epage committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    18a5940 View commit details
    Browse the repository at this point in the history