fix(release): run git-cliff via uvx and allow a manual re-cut - #434
Merged
Merged
Conversation
The first run of the new release workflow failed at startup: this repository's Actions policy allows only GitHub-owned, verified-creator, and allowlisted actions, and orhun/git-cliff-action is not on the list. The release job now runs git-cliff from PyPI through uvx (the same binary, no third-party action), so nothing in the pipeline depends on the allowlist beyond actions/* and astral-sh/setup-uv. Also adds workflow_dispatch (bump: patch|minor|major, build_binaries) so a release can be re-cut from the current main by hand after a failed run, instead of needing another merge.
ishandhanani
requested review from
alec-flowers,
csahithi and
nlevin-ui
as code owners
September 13, 2026 22:30
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.
Why
The first run of the new release pipeline (#430 merge, run 34786736507) died with
startup_failurebefore any job ran: the repository's Actions policy isselected(GitHub-owned, verified creators, and an allowlist), andorhun/git-cliff-actionis not allowed. Nov2.0.0was cut.What
uvx git-cliff==2.13.1 --config cliff.toml --latest --strip all --github-repo ... --output notes-body.mdinstead of the action. Same tool, same notes, no third-party action.workflow_dispatchwithbump(patch / minor / major) andbuild_binariesso a release can be re-cut frommainby hand after a failure.On merge
This PR touches
release.yaml, which the workflow treats as a binary-affecting change, so both Rust binaries are rebuilt and report the new tag from--version.BREAKING CHANGE: cuts the v2.0.0 release line. The breaking change itself landed in #407 (recipe schema 2,
--bashremoved) and its tag was lost to the failed run above; this merge produces thev2.0.0tag that #430 was meant to.