You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bump the root package.json version from 2.4.0 to 2.5.0 on v2/main, ahead of the v2.5.0 milestone merge into main.
Why
Per the release skill, the version bump is part of the milestone's work and belongs on the develop branch (v2/main), so it flows into main with everything else. Doing it on the milestone-merge branch instead leaves v2/main reading a stale version and risks the bump leaking into unrelated PRs (#2010).
Scope
Root package.json: 2.4.0 → 2.5.0 (there is one version number in the repo; the clients carry none).
package-lock.json updated by npm version minor --no-git-tag-version.
No tag is created here — the release tag points at the merge commit on main, cut separately.
Activity
chore: bump version to 2.5.0 (#2213)
cliffhall commentedon Sep 1, 2026
Shipped in #2213 (merged as fe35885).
v2/mainnow reads 2.5.0.[-]chore: bump version to 2.5.0[/-][+]Release 2.5.0 step 1: bump version to 2.5.0[/+]