Add SemVer violation check to publishing CI workflow #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This tool has a number of false negatives and may not catch all the violations.
miax-gevu
approved these changes
Feb 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This tool will review the API against the latest version already released on crates.io and try to check if there is a SemVer violation (whether crate version changed properly or not).
Important note
This tool has quite a few false negatives and may not catch all the violations. E.g. adding new item (function, structure) to a public API doesn't trigger minor update.
You should still watch out for SemVer manually. If this step at CI is green it doesn't mean that everything is fine.
However I think that it's still better to have it here that not to have it: it may catch at least something and warn you on time.