refactor: release-PR flow with auto-release on merge to main#52
Merged
Conversation
Replace the all-in-one release workflow with two simple ones: - release-pr (dispatch): bump version files, open release/vX.Y.Z PR. - release (push to main): release when the version has no tag yet, then test, publish to PyPI + MCP Registry, deploy to the VPS, and finally tag and create the GitHub release. Production now always deploys what is on main, and each tag points at a real main commit. Drops the dual trigger, prepare/validate/ finalize-tag/sync-main branch juggling, and the first-release tag_only path. PyPI publish uses skip-existing for safe re-runs.
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.
Summary
Simplifies releases to the standard release-PR pattern and fixes two defects in the prior design (deploying/tagging from an unmerged
release/*branch).release-pr.yml(workflow_dispatch): bump version files, openrelease/vX.Y.ZPR tomain. No publish/deploy.release.yml(push: main): if the current version has no tag yet →check→test→publish-pypi→publish-mcp-registry+deploy(parallel) →finalize(tag + GitHub release).gate,prepare,validate-version,finalize-tag,sync-main, the dual trigger, and thetag_onlyfirst-release path (0.1.0 already shipped).skip-existing: true; registry publish already idempotent → failed runs are safely re-runnable.bump_version.pydrops the unusedallow_unchanged/tag-only coupling.publishing.md,distribution.md) updated.Why it's better
main; everyvX.Y.Ztag points at a realmaincommit.GITHUB_TOKENtag-push events — no PAT needed.Test plan
pytest -q(262 passed)actionlinton all workflows