ci: signal release readiness when a version milestone completes - #41
Merged
Merged
Conversation
pmaxhogan
enabled auto-merge (squash)
June 26, 2026 15:04
Contributor
Coverage
Gate: passed - no coverage regression (epsilon 0.1 pp). |
Adds .github/workflows/release-ready.yml. When every issue in a version milestone (v0.3.0, v1.0.0, ...) is closed, it comments on + labels the open release-please PR and @-pings the maintainer to review + merge it. Signal-only by design - it NEVER auto-merges: a GITHUB_TOKEN bot merge would not trigger release-please.yml/release.yml, so no v* tag would be cut and nothing would ship. Pairs with the new GitHub Project roadmap (milestones = versions). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CyiRqk2DVwmJjEu5gcD1m
pmaxhogan
force-pushed
the
feat/release-ready-signal
branch
from
June 26, 2026 15:47
150df61 to
86b39dc
Compare
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.
Pairs with the new GitHub Project roadmap (github.com/users/pmaxhogan/projects/1), where versions are tracked as milestones (v0.3.0, v1.0.0, v2.0.0).
When every issue in a version milestone is closed, this workflow comments on + labels (
ready-to-release) the open release-please PR and @-pings me so I review the computed version + CHANGELOG and merge it myself.Signal-only by design - it never merges anything. A bot merging the release PR with
GITHUB_TOKENwould not triggerrelease-please.yml/release.yml(token-authored events start no workflow run), so no tag would be cut and nothing would actually ship. Milestone titles are also just planning labels (release-please computes the real version from commits), and milestone-100% says nothing about CI being green. So the merge stays a human click; this just removes the "did I notice the version is done?" gap.Triggers:
issues: closed(precise), a dailyschedulebackstop, andworkflow_dispatch. Dedups per-milestone via a hidden sentinel comment. UsesGITHUB_TOKENonly (no PAT). Validated with actionlint.🤖 Generated with Claude Code
https://claude.ai/code/session_012CyiRqk2DVwmJjEu5gcD1m