Add cargo-semver-checks v0.15.0 release notes

[obi1kenobi]

The 0.15.0 release of cargo-semver-checks contains a massive number of improvements. I would like to get your thoughts on whether including the release notes in the "Project/Tooling Updates" section would be an appropriate way to communicate this to the TWIR readers, or if there's something else you'd recommend instead.

Thanks again for all the awesome work you're doing!

[U007D]

Thank for your contribution, @obi1kenobi! Per our submission guidelines, we tend not to accept links to change logs or links to code repositories. The newsletter seeks to engage its readership with engaging story-form content and learning material.

Please feel free to announce these changes on /r/rust subreddit, in HackerNews, etc.

Best regards,
TWiR Editors

[obi1kenobi]

Got it, thank you!

[U007D]

Taking note of other submissions, it is worth noting that we do publish changelogs for rust-analyzer and IntelliJ Rust. This is because they have an impact on so many Rust users, possibly even a majority of them. If you feel this crate or another is worthy of this kind of consideration, please do not hesitate to let us know.

Thanks again!

[obi1kenobi]

Of course, I leave the final editorial decision to you. Here's why I personally think cargo-semver-checks may be worth including:

• While cargo-semver-checks is currently an external crate, the cargo team has decided to merge it into cargo and make it a first-party command just like cargo check or cargo test`. At that point, its release notes will be in scope as part of the "Updates from the Rust Project" section.
• Proper semver versioning is critical for the Rust ecosystem since it's a foundational assumption in cargo. Yet it's very easy to accidentally violate semver via a seemingly-innocuous code change, and when such an accident happens in a popular library (clap, pyo3, etc.) then the entire ecosystem bears the consequences: broken builds, forced upgrades, yanked versions, etc.
• While it isn't as pervasive as rust-analyzer yet, cargo-semver-checks is undoubtedly entering the Rust mainstream: significant Rust projects are adopting it, it's included in nixos-22.11, and users of release-management tools are requesting that those tools integrate with cargo-semver-checks.

There are hundreds, if not thousands, of different ways one might accidentally violate semver. Today, cargo-semver-checks can only catch a subset of them — though that subset grows with every release. Library maintainers are responsible for ensuring their crates follow semver, and the cargo-semver-checks release notes can help them keep track of which checks have been automated away thus far.

Thanks for your consideration, and of course, no hard feelings if you decide the project hasn't met the bar yet. I firmly believe that one day soon, automated semver-checking will be the norm just as much as cargo test is today, and I am committed to being a part of making that happen.