Skip to content

chore(contract): declare release_mode pull_request#59

Merged
MCamner merged 1 commit into
mainfrom
chore/declare-release-mode
Jul 19, 2026
Merged

chore(contract): declare release_mode pull_request#59
MCamner merged 1 commit into
mainfrom
chore/declare-release-mode

Conversation

@MCamner

@MCamner MCamner commented Jul 19, 2026

Copy link
Copy Markdown
Owner

main is branch-protected here, so a release cannot be pushed directly.

Declaring release_mode means mq-agent refuses knowingly before any
mutation
, rather than discovering the rule from a GH013 push error after
the bump, commit and tag already exist locally — which is exactly what happened
releasing mq-agent v1.23.0 and had to be unwound by hand.

Contract added by mq-agent#157; the closed value set (direct,
pull_request, manual) by mq-agent#160.

pull_request blocks execute today. The PR-mediated release path (release
branch → PR → tag the merged commit) is a separate slice.

🤖 Generated with Claude Code

main is branch-protected here, so a release cannot be pushed directly.
Declaring it means mq-agent refuses knowingly before any mutation rather
than discovering the rule from a GH013 push error after the bump, commit
and tag already exist locally — which is what happened releasing
mq-agent v1.23.0.

pull_request blocks execute today. The PR-mediated release path (release
branch -> PR -> tag the merged commit) is a separate slice.
@MCamner
MCamner merged commit c8be9ca into main Jul 19, 2026
3 checks passed
@MCamner
MCamner deleted the chore/declare-release-mode branch July 19, 2026 13:16
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