ci: add a republish lever for tagged releases whose publish failed - #4
Merged
Conversation
release-please will not re-emit an already-tagged release, so a publish that fails after tagging is unreachable for both the driver and the daily sweep. The workflow_dispatch trigger now takes a republish input naming an existing tag: such a run skips the driver, checks out the tag, and publishes that one package over OIDC. Mirrors the sibling headerless repository. RELEASING.md documents the lever.
firejune
enabled auto-merge (squash)
August 23, 2026 11:25
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.
Same lever as firejune/headerless#14: release-please will not re-emit an already-tagged release, so a publish that fails after tagging is unreachable for both the zero-touch driver and the daily sweep. The
workflow_dispatchtrigger now takes an optionalrepublishinput naming an existing tag; such a run skips the driver, checks out the tag, and publishes that one package over OIDC (one tag per run). Empty input keeps every existing path byte-identical. RELEASING.md documents the lever.