Repository navigation
ci(release): publish a tag only from green CI, and re-drive by tag input - #156
Merged
Merged
Conversation
The release workflow no longer lints or tests at the tag. It requires the tagged commit's ci.yml, ecosystem-gate.yml, live-smoke.yml and fuzz.yml push runs to have succeeded (waiting up to an hour for them), checks the tag against the crate versions, and publishes guard-core-engine then guard-core-rs through trusted publishing, skipping a version already on crates.io. A manual run takes a tag input and checks that tag out, so master's workflow can publish an existing tag after a partial failure without turning trusted publishing off.
This was referenced Oct 16, 2026
Merged
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.
Closes #155
v4.4.0 failed its release gate on a lint that pull request CI never ran, after the tag was already immutable, and the workflow_dispatch path could not re-drive it from master because the tag check read GITHUB_REF_NAME. Both crates ended up published by hand with trusted publishing turned off.
This release workflow runs no lint or test of its own:
taginput, checks it out, compares it to the guard-core-engine and guard-core-rs versions, and requires the newest push run of ci.yml, ecosystem-gate.yml, live-smoke.yml and fuzz.yml on that commit to have succeeded (it waits up to an hour, so a release created right after a merge does not fail).A re-drive is Actions > Release > Run workflow with the tag; it checks the tag out with master's fixed workflow. The trusted publisher entries match on repository and workflow file (release.yml, no environment), which are unchanged.
Tested locally: actionlint clean. The CI check run against the real commits: v4.4.0 (e9783d5) and be51b52 pass with all four workflows green; b3b7128, whose CI failed, is refused with
ci.yml concluded failure. After merging I will dispatch it with tag v4.4.0 to prove the re-drive path end to end; both crates are already on crates.io, so the publish step skips them.