rust
/
cargo
mirror of https://github.com/rust-lang/cargo
0
0
Fork 0
Code Issues Releases Wiki Activity

Auto merge of #13015 - ehuss:bump-stable-0.75.1, r=weihanglo 

[stable 1.74] Bump cargo patch version

https://github.com/rust-lang/cargo/pull/13004 bumped the credential crate versions to deal with a semver-incompatible change, but I believe we also need to bump and publish cargo.

My thinking is that:
* cargo 0.75.0 currently depends on cargo-credential-libsecret="0.3.1"
    * The `Cargo.lock` is locked to **0.3.2**
* We plan to yank cargo-credential-libsecret 0.3.2
* Users who depend on cargo 0.75.0 as a library will be unable to do so since after yanking it will pick up cargo-credential-libsecret="0.3.1", but this won't work.
    * cargo 0.75.0 -> cargo-credential 0.4.0
    * cargo-credential-libsecret 0.3.1 -> cargo-credential **0.3.0**

(Users using a `Cargo.lock`, like doing rust builds, shouldn't be affected by the yank.)

So, after publishing the new credential crates, I think we'll also need to publish a new 0.75.1 which depends on the correct versions so that users can use 0.75. It also probably makes sense to yank 0.75.0.
This commit is contained in:
bors 2023-11-20 03:04:43 +00:00
parent 5c8a2842e0 b08c2084e9
commit 130825286f
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Cargo.lock generated
View File

@ -234,7 +234,7 @@ dependencies = [
[[package]]
name = "cargo"
version = "0.75.0"
version = "0.75.1"
dependencies = [
"anstream",
"anstyle",

2
Cargo.toml
View File

@ -105,7 +105,7 @@ windows-sys = "0.48"
[package]
name = "cargo"
version = "0.75.0"
version = "0.75.1"
edition.workspace = true
license.workspace = true
homepage = "https://crates.io"