You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand the reasoning, just that the release notes for 0.3.75 on GH indicate that 1.79 is the MSRV, as well as the Cargo.toml for commit tagged '0.3.75', whereas the release of 0.3.75 on crates.io says 1.82.
That is #712. Seems that when 0.3.75 was tagged, it didn't get released to crates.io and when release-plz got setup, the current commit on master got released as 0.3.75 to crates.io.
That is #712. Seems that when 0.3.75 was tagged, it didn't get released to crates.io and when release-plz got setup, the current commit on master got released as 0.3.75 to crates.io.
Thanks for looking, wanted to point it out, just in case anyone comes here. 🙂
Only reason I noticed was because we had some CI/CD pipeline issues due to the bump of the MSRV (thinks that's a different issue though)
Activity
bjorn3 commentedon May 8, 2025
The MSRV was bumped to 1.82 in #700
danielfeather commentedon May 8, 2025
I understand the reasoning, just that the release notes for 0.3.75 on GH indicate that 1.79 is the MSRV, as well as the Cargo.toml for commit tagged '0.3.75', whereas the release of 0.3.75 on crates.io says 1.82.
bjorn3 commentedon May 8, 2025
That is #712. Seems that when 0.3.75 was tagged, it didn't get released to crates.io and when release-plz got setup, the current commit on master got released as 0.3.75 to crates.io.
danielfeather commentedon May 8, 2025
Thanks for looking, wanted to point it out, just in case anyone comes here. 🙂
Only reason I noticed was because we had some CI/CD pipeline issues due to the bump of the MSRV (thinks that's a different issue though)