Repository navigation
ci: run release-plz update in pull requests - #2194
Merged
Merged
Conversation
Before merge, check that every published crate resolves its dependencies from crates.io (where cargo-semver-checks failed on main over a yanked version), then run release-plz update with semver checks off. Takes minutes, not the half hour a full semver check does. Fixes #2165 Signed-off-by: Luca Muscariello <muscariello@ieee.org>
Signed-off-by: Luca Muscariello <muscariello@ieee.org>
muscariello
changed the title
Drop the custom dependency-resolution script; run release-plz update with semver checks off, on a detached checkout (supported since 0.3.169). Signed-off-by: Luca Muscariello <muscariello@ieee.org>
lgecse
approved these changes
Oct 9, 2026
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
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.
Fixes #2165.
New
release-plz updatejob on pull requests and merge-queue entries (skipped on push, whererelease-rust.yamlruns the real thing). Same release-plz version as the release workflow; no Rust setup needed.Semver checks are off: they take ~30 min, and release-plz can only disable them in its config, so the job runs from a copy with
semver_check = false. As a result it doesn't catchcargo-semver-checksfailures like the Sep 29 one (yanked dependency).