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

feat: make lockfile v4 the default #14595

Merged
merged 3 commits into from
Sep 25, 2024
Merged

Commits on Sep 24, 2024

  1. Configuration menu
    Copy the full SHA
    f30f909 View commit details
    Browse the repository at this point in the history
  2. test(lockfile): default lockfile version is still v3

    It will become v4 when we changes the default.
    weihanglo committed Sep 24, 2024
    Configuration menu
    Copy the full SHA
    f3672cb View commit details
    Browse the repository at this point in the history

Commits on Sep 25, 2024

  1. feat: make lockfile v4 the default

    This commit makes lockfile version 4 the default version when Cargo
    tries to write to a lockfile.
    
    The lockfile version 4 has been stabilized since 1.78.0,
    and will become default in 1.83.0.
    the length of transition period is pretty similar as before.
    
    One caveat is that in other output from Cargo,
    e.g., `cargo metatada`, status messages,
    `SourceID` will display in the v4 URL encoded format.
    This shouldn't affect the majority of Rust users,
    as `SourceId` representation should be opaque to them,
    unless comparing `SourceId` across different version of toolchains.
    weihanglo committed Sep 25, 2024
    Configuration menu
    Copy the full SHA
    5dfdd59 View commit details
    Browse the repository at this point in the history