ci(release): remove 'version bump' label gate - #41
Merged
Conversation
… main Simplifies the release flow. Any PR merged to main now produces a release if it contains .changeset/*.md in its diff. The 'version bump' label is no longer required. Changes: - release.yml: drop the 'contains(..., labels.*.name, "version bump")' condition from the job 'if'. PR-closed-on-main is the only condition. - CLAUDE.md: update Branching Strategy to drop the label requirement. - CONTRIBUTING.md: same. - release-system.md (plan): update Section 3, Decision log, and YAML example to match the simplified flow. The 'has_changesets' detection step is the only safety net: a merge to main without changesets is a no-op (the publish steps are gated on it). Adds a changeset to pass the new ci.yml lint.
martyy-code
added a commit
that referenced
this pull request
Aug 3, 2026
…ronment) Adds Section 7 (Trusted publishing & environment) to the plan and a matching Appendix C (Post-plan decision log). Two items are added to the Definition of done: - At least one release has been published via npm trusted publishing (OIDC), per Section 7.1. - The GitHub 'release' environment exists with at least one deployment record, per Section 7.2. Plan Status also moves from 'Proposed' to 'Approved and partially implemented on staging' because Phases 3, 4, 5 plus Section 7 are now merged on the staging branch (PRs #40, #41, #42).
This was referenced Aug 3, 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
Follow-up to PR #40. Removes the
version bumplabel gate from the release workflow. Every PR merged tomainnow produces a release if it contains.changeset/*.mdin its diff.Why
PR #40 left the label gate in place. The release engineer still had to remember to apply the
version bumplabel on every release PR. That is cognitive load with no safety benefit — thehas_changesetsdetection step already makes merges-without-changesets a no-op. Removing the label simplifies the flow.What changes
.github/workflows/release.yml— drop thecontains(..., labels.*.name, 'version bump')condition. PR-closed-on-main is the only condition.CLAUDE.md— update Branching Strategy.CONTRIBUTING.md— same.docs/internal/engineering/plans/release-system.md— update Section 3, Decision log, and YAML example to match the simplified flow..changeset/remove-version-bump-label.md— required by the ci.yml lint.Effect
Before: a merge to
mainwithout theversion bumplabel is silent.After: a merge to
mainwith at least one.changeset/*.mdpublishes a release. A merge without changesets is still a no-op.🤖 Generated with Claude Code