cargo-semver-checks 0.7.0 has some new checks:
๐ค `pub use` re-exports
โก auto-trait impls (Sync, Sized, ...)
๐ impl of derived traits
No more #rustlang auto-trait regressions! ๐ฏ Add an Rc<T> field โ oops, your type isn't Send/Sync anymore. So easy to miss, but not anymore.
๐ค `pub use` re-exports
โก auto-trait impls (Sync, Sized, ...)
๐ impl of derived traits
No more #rustlang auto-trait regressions! ๐ฏ Add an Rc<T> field โ oops, your type isn't Send/Sync anymore. So easy to miss, but not anymore.
A few months ago, @nikomatsakis wondered on his blog if we could have a simple GitHub Action that would warn about semver regressions.
That GitHub Action is here:
- uses: obi1kenobi/cargo-semver-checks-action@v1
smallcultfollowing.com/babysteps/blogโฆ
That GitHub Action is here:
- uses: obi1kenobi/cargo-semver-checks-action@v1
smallcultfollowing.com/babysteps/blogโฆ
Semver accidents happen. cargo-semver-checks saved me from one just two days ago. clap v3.2.6 had one a few months ago due to auto-traits:
github.com/clap-rs/clap/iโฆ
cargo-semver-checks could have prevented the clap accident too, if it had existed at the time.
github.com/clap-rs/clap/iโฆ
cargo-semver-checks could have prevented the clap accident too, if it had existed at the time.
Are you a crate maintainer considering it? What do you need to get to "definite yes?" DMs open if you'd prefer to share privately.
I'm planning to spend the next couple of weeks on UX improvements and maybe a blog post on how this all works โ there's fun stuff under the hood!
I'm planning to spend the next couple of weeks on UX improvements and maybe a blog post on how this all works โ there's fun stuff under the hood!
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
ใ
