Semver-checks for all crate on merge and push #16078
Open
+128
−0
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
github-actions
bot
added
the
development-process
|
|
logan-keede
changed the title
|
cc @crepererum |
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.
Which issue does this PR close?
cargo-semver-checks#15408cargo semver-checksfor release testing #13665Rationale for this change
Detect accidental breaking changes.
What changes are included in this PR?
A github workflow, that uses
cargo semver-checksfor all crates. divided into three parts because 1 job goes on for too long + crashes before completion(can probably be fixed by emptying/deleting cache in the middle.)Are these changes tested?
On local branch by CI.
Are there any user-facing changes?
NO.