Open
Conversation
Iizuki
commented
Jan 23, 2026
Contributor
Author
There was a problem hiding this comment.
This is the new bit.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The PR is broken off of #13, and depends on it too (so as to avoid convoluted git incantations). The only new change is cargo-semver-checks in the release workflow.
It lints the crate for semver violations before making a release.
It's not the most crucial thing in a crate with only a small API but in general it's a good practice, as SemVer violations can be quite subtle. It makes crates more dependable.