cargo-semver-checks
cargo-semver-checks copied to clipboard
obi1kenobi
Scan your Rust crate for semver violations.
Needs Trustfall support for tagging a value inside a `@fold` and then using it outside the fold. The query for "the import specifically is missing, but the item is present"...
The API extends past the rust code to the manifest Possible checks include - Explicit feature removed (major breaking) - Implicit feature (optional dependency) removed (informative) - This is separate...
Requires at least - #53 - #52 But would also benefit from #51, #50
The language needs to convey that this is incomplete as - Not all checks are written - There are semantic breaking changes that are not checked
Sometimes it's useful to be able to change the alert level of specific lints for a particular item or an entire module. Clippy and rustc lints have already stabilized syntax...
Like #6 being an output mode, this would be another that would provide a snippet for including in a changelog. No-touch additions (automatically insert into file, using a particular users...
Technically, semver says that these are minor changes. Not all want to treat it as such and is an example of why people would want control over lints treatments, see...
### Steps to reproduce the bug with the above code 1. `cargo init --lib` 2. `commit everything` 3. Change files to get this: ``` > git diff diff --git a/src/lib.rs...
I believe that the tool will fail when it'll try to generate rustdoc of a yanked release from registry. Basically `cargo` (correctly) refuses to use a yanked release of a...
