fix(ci): force-push the throwaway release branch so retries aren't blocked - #163
Conversation
Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reached
On-demand reviews are free for the next 21 days. After that, they cost $0.25 per reviewed file. Or wait 9 minutes for your next included review. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Warning Your free Security trial is over. An organization admin can activate Security or dismiss this notice. Comment |
Problem
Release run 33329333792 failed in Commit version bump:
An earlier failed run (33329114653) had already created and pushed
release/v0.1.2before dying at the merge step. The retry recomputes the same version, builds the same branch name from a fresh commit, and its push is therefore a non-fast-forward against the leftover branch. Every retry at the same version hits this — the workflow is blocked by its own debris.Fix
Force-push the throwaway release branch. It only ever carries the version bump for that exact tag and is deleted by
gh pr merge --delete-branchon success, so overwriting a leftover copy is safe.I also deleted the stranded
release/v0.1.2branch so the next run starts clean.Verification
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/release.yml'))"parses cleanly. CI configuration only; no code changes, so no tests were run.Follow-up to #160 and #161.