Run cargo-semver-checks in CI for every pull request. This is to ensure we do not accidentally break the API of our crates (again 😅).
When a PR does break the api it should be flagged with the "breaking change" label. If that is done, the check will be skipped. The next release after merging that PR needs to update the version accordingly.
Run
cargo-semver-checksin CI for every pull request. This is to ensure we do not accidentally break the API of our crates (again 😅).When a PR does break the api it should be flagged with the "breaking change" label. If that is done, the check will be skipped. The next release after merging that PR needs to update the version accordingly.
Examples of the CI catching breakages:
Example of the job being skipped: