Skip to content

ci: fix release job (git pull tracking) so Automated Release doesn't fail#35

Merged
antonbabenko merged 1 commit into
masterfrom
ci/release-flow-fix
May 24, 2026
Merged

ci: fix release job (git pull tracking) so Automated Release doesn't fail#35
antonbabenko merged 1 commit into
masterfrom
ci/release-flow-fix

Conversation

@antonbabenko
Copy link
Copy Markdown
Owner

Follow-up to #34. The release job did git checkout -B release/next (no upstream), so the changelog action's git pull --ff-only failed at setup - Automated Release errored on the #34 merge. Fix: stay on master (has tracking); the action pushes to release/next via its git-branch input. Adds --delete-branch on auto-merge. ci: commit, so merging it won't cut a release - it should make Automated Release skip cleanly instead of failing.

The reset step did 'git checkout -B release/next', an upstream-less branch, so the action's internal 'git pull --ff-only' failed ('no tracking information'). Stay on master (has tracking); the action pushes the release commit to release/next via its git-branch input. Also delete the merged release/next after auto-merge.
@antonbabenko antonbabenko merged commit fa68d99 into master May 24, 2026
1 check passed
@antonbabenko antonbabenko deleted the ci/release-flow-fix branch May 24, 2026 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant