chore(release): bump v4-next to 4.4.0#23307
Merged
Merged
Conversation
Sibling to the v4.3.0-rc.1 release PR. After v4-next is merged into v4 for v4.3.0-rc.1, v4-next opens its next minor cycle at 4.4.0. Skipping precommit hook: a pre-existing bug in yarn-project/precommit.sh mis-detects root-only json edits, then prettier fails because it looks for the file from yarn-project/. The file is already correctly formatted.
alexghr
approved these changes
May 15, 2026
This was referenced May 19, 2026
aminsammara
added a commit
that referenced
this pull request
May 20, 2026
## Summary Re-applies the v4-next minor-cycle bump from `4.3.0` → `4.4.0`. The original bump (#23307) was silently undone when `pull-v4-into-v4-next.yml` fast-forwarded `v4-next` onto `v4` after the v4.3.0 release merges. ## What happened 1. #23307 set v4-next's manifest to `4.4.0` (May 15). 2. The "merge v4-next into v4 for v4.3.0-rc.2 release" merge (88ef5ca) resolved the manifest conflict in favor of v4's `4.3.0` — the correct call for v4, but it left v4 ahead of v4-next on every file except the manifest. 3. `pull-v4-into-v4-next.yml` triggered on the subsequent pushes to v4 and ran `git merge origin/v4 --no-edit` while on v4-next. Because v4-next's tip was an ancestor of v4's tip (v4 already had v4-next as a parent of the merge), the merge fast-forwarded v4-next to v4 — overwriting the 4.4.0 manifest with `4.3.0`. 4. `origin/v4` and `origin/v4-next` now point to the same commit (`54564b4d53`). ## Follow-up (separate PR) The auto-sync workflow should preserve `.release-please-manifest.json` from `v4-next` when merging v4 → v4-next (e.g. `git checkout --ours .release-please-manifest.json` after the merge, or fail the workflow if the manifest version regresses). I'll send that as a separate change. ## Test plan - [ ] CI green - [ ] After merge, confirm `.release-please-manifest.json` on `v4-next` reads `4.4.0` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
Sibling to the v4.3.0-rc.1 release PR (#23306), which merges v4-next into
v4 and ships at manifest `4.3.0`. After that lands, this PR opens
v4-next's next minor development cycle at `4.4.0`.