Summary
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.
Acceptance
Summary
Bump the root
package.jsonversion from2.4.0to2.5.0onv2/main, ahead of the v2.5.0 milestone merge intomain.Why
Per the
releaseskill, the version bump is part of the milestone's work and belongs on the develop branch (v2/main), so it flows intomainwith everything else. Doing it on the milestone-merge branch instead leavesv2/mainreading a stale version and risks the bump leaking into unrelated PRs (#2010).Scope
package.json:2.4.0→2.5.0(there is one version number in the repo; the clients carry none).package-lock.jsonupdated bynpm version minor --no-git-tag-version.No tag is created here — the release tag points at the merge commit on
main, cut separately.Acceptance
package.jsonreads2.5.0onv2/mainv2.5.0git tag created by the bumpnpm run local:gatepasses