ci: restore auto-bump release (revert tag-only #8)#12
Merged
Conversation
Effectively reverts #8 (tag-only, manual-bump release). The release app has been re-added with a ruleset bypass, so the workflow can once again push the version-bump commit + tag directly to protected main. - Restore the `bump` dispatch input (patch/minor/major, default patch). - Mint a GitHub App installation token and checkout/push as the app (bypasses the "Protect main" ruleset that GITHUB_TOKEN cannot). - semantic-release writes the new version to pyproject.toml + __init__.py, tags v<version>, regenerates the changelog, then we regenerate uv.lock, amend, and push commit + tag to main. - Drop the manual-bump re-release guard and the separate tag-release job (the tag now travels with the bump commit). Public PyPI publishing (OIDC Trusted Publishing) and the best-effort GHCR image are kept. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Claude finished @akshaylive's task in 1m 17s —— View job Code Review in Progress
|
bai-uipath
approved these changes
Jul 9, 2026
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
2 participants
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.
Summary
Restores the auto-bump release behavior (the model still live in
coder_eval.bak), effectively reverting #8. The release GitHub App has been re-added with a ruleset bypass, which removes the reason #8 dropped auto-bump in the first place (GH013— plainGITHUB_TOKENcan't push the bump commit to ruleset-protectedmain).What changes
bumpdispatch input is back (patch/minor/major, defaultpatch).RELEASE_APP_ID/RELEASE_APP_PRIVATE_KEY), checkout + push as the app so the bump commit + tag land on protectedmainvia the app's ruleset bypass.pyproject.toml+__init__.py, tagsv<version>, regenerates the changelog; we then regenerateuv.lock, amend, and push commit + tag.tag-releasejob — the tag now travels with the bump commit.Kept
publish-pypijob.Release flow after this
Actions → Release → pick bump level → workflow bumps + tags + pushes to
main, builds, publishes to PyPI, pushes the GHCR image. No more manual "bump version via PR first" step.🤖 Generated with Claude Code