chore: make stable release manual-dispatch only#2085
Merged
Conversation
Remove the vX.Y.Z tag push trigger from the publish workflow; pushing release tags is not permitted, so stable releases are cut only via workflow_dispatch with an existing tag. The main-branch dev pre-release path is unchanged. Also drops the now-dead tag-push code paths in the build-tag job. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ApprovabilityVerdict: Approved This PR makes a minor CI/CD workflow adjustment, removing automatic tag-push triggers for stable releases and requiring manual dispatch instead. The change is self-contained, doesn't affect runtime behavior, and simplifies the release process. You can customize Macroscope's approvability policy. Learn more. |
JannikSt
approved these changes
Jul 20, 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
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
vX.Y.Ztag push trigger from the Publish verifiers workflow — pushing release tags is not permitted, so stable releases are now cut only viaworkflow_dispatchwith an existing tag.build-tagjob accordingly: single dispatch-only checkout, and the tag resolution step readsinputs.tagdirectly (dropping the now-dead push-ref branch).build-dev/publish-dev) is unchanged.Breaking
vX.Y.Ztag no longer triggers a PyPI publish or GitHub release. To cut a stable release, run the Publish verifiers workflow viaworkflow_dispatchwith the existing tag as input.🤖 Generated with Claude Code
Note
Medium Risk
Changes how production PyPI/GitHub releases are triggered; teams that relied on pushing
vX.Y.Ztags must switch to manual workflow dispatch or releases will not ship.Overview
Stable
verifiersreleases no longer run on tag push — only Publish verifiers viaworkflow_dispatchwith an existingvX.Y.Ztag publishes to PyPI and creates the GitHub release (aligned with tag pushes not being allowed).The
on.push.tagstrigger is removed frompublish-verifiers.yml. Thebuild-tagjob is gated to dispatch only, uses a single checkout ofrefs/tags/${{ inputs.tag }}, and resolves the release tag frominputs.taginstead of branching on push vs dispatch.Unchanged: pushes to
mainstill drive dev pre-releases (build-dev/publish-dev).Reviewed by Cursor Bugbot for commit 049c396. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Restrict stable release workflow to manual dispatch only
vX.Y.Ztag-push trigger from publish-verifiers.yml; stable releases now require an explicitworkflow_dispatchwith a tag input.build-tagjob by removing tag-push event logic and always checking outrefs/tags/${{ inputs.tag }}.vX.Y.Ztag no longer triggers a stable release; the workflow will fail ifinputs.tagis absent or does not matchvX.Y.Z.Macroscope summarized 049c396.