chore(release): re-bump v4-next to 4.4.0#23423
Merged
Merged
Conversation
The earlier 4.4.0 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, inheriting v4's 4.3.0 manifest. Re-open v4-next's next minor development cycle at 4.4.0.
alexghr
approved these changes
May 20, 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
Re-applies the v4-next minor-cycle bump from
4.3.0→4.4.0. The original bump (#23307) was silently undone whenpull-v4-into-v4-next.ymlfast-forwardedv4-nextontov4after the v4.3.0 release merges.What happened
4.4.0(May 15).4.3.0— the correct call for v4, but it left v4 ahead of v4-next on every file except the manifest.pull-v4-into-v4-next.ymltriggered on the subsequent pushes to v4 and rangit merge origin/v4 --no-editwhile 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 with4.3.0.origin/v4andorigin/v4-nextnow point to the same commit (54564b4d53).Follow-up (separate PR)
The auto-sync workflow should preserve
.release-please-manifest.jsonfromv4-nextwhen merging v4 → v4-next (e.g.git checkout --ours .release-please-manifest.jsonafter the merge, or fail the workflow if the manifest version regresses). I'll send that as a separate change.Test plan
.release-please-manifest.jsononv4-nextreads4.4.0🤖 Generated with Claude Code