chore(release): bump version to v2.0.4#278
Merged
Merged
Conversation
Closes the bump-back chain manually. PR title matches the loop-guard regex so the release triggered by this merge will skip cleanly, leaving master and npm both at v2.0.4.
bradtaylorsf
added a commit
that referenced
this pull request
May 27, 2026
* fix(config): default project to 0 so removing the YAML key disables the board The previous default of 2 meant that omitting the project: line in .alpha-loop.yaml silently fell back to project number 2 (this repo's own board), instead of disabling project board transitions. With project: 0 every project-related call site short-circuits cleanly: - pollIssues falls back to label-based polling - updateProjectStatus returns early - ensureProjectStatuses logs "No project board configured — skipping" - addIssueToProject is guarded at every call site Also comments out project: 2 in this repo's own .alpha-loop.yaml since the board isn't actively used. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * ci(release): switch to bump-in-PR deploy flow Replaces the "CI stamps version + opens bump-back PR" model with a local-first flow that eliminates the two-PR cascade and the infinite-loop risk we hit on the v2.0.0 → v2.0.4 chain. New flow: - pnpm deploy (local): computes next semver from conventional commits, stamps package.json, opens a release PR with the bump already in it. - CI: just publishes whatever version is in package.json after merge. Gates on "package.json version != latest tag" — if they match, skip. - pnpm release:watch: tails the workflow run, verifies local == npm == tag after publish, pulls master so local stays in sync. Removed from the workflow: - "Stamp version" step (no longer rewriting package.json in CI) - "Sync version bump back to master via PR" step (no follow-up PR needed) - Loop guard regex (no possible cascade — version bump and feature are in the same merge commit) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(release): release v2.0.5 - c869883 ci(release): switch to bump-in-PR deploy flow - 9864509 fix(config): default project to 0 so removing the YAML key disables the board - aacb191 chore(release): bump version to v2.0.4 (#278) - f725af8 chore(release): bump version to v2.0.3 (#275) --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Closes the bump-back chain. PR title matches the loop-guard regex, so the release fired by this merge will skip cleanly. After this lands, master and npm will both be at v2.0.4.