Automatically check semVer compatibility in CI #713
Merged
Conversation
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
nicoburns
approved these changes
Jan 13, 2026
Contributor
nicoburns
left a comment
nicoburns
left a comment
There was a problem hiding this comment.
Seems like a good idea. Do we need some logic to also remove the other label?
I'm thinking of cases where a PR is pushed to, and it's breaking vs. non-breaking status changes...
Signed-off-by: Simon Wülker <simon.wuelker@arcor.de>
simonwuelker
force-pushed
the
semver-ci-checks
branch
from
76041e1 to
9fd1a8d
Compare
Contributor
Author
|
I've added a line that removes both labels before assigning the new one. |
Signed-off-by: Simon Wülker <simon.wuelker@arcor.de>
Contributor
Author
|
Permissions work fine on my fork, so I think the job is (correctly) failing while the job is not in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 action will automatically assign the "breaking" or "non-breaking" to PRs based on the output of
cargo-semver-checks.Testing: I opened two test PRs in my fork, which were labelled correctly (https://github.com/simonwuelker/html5ever/pulls)