Skip to content

Release 2.5.0 step 1: bump version to 2.5.0 #2212

Closed

Description

@cliffhall

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

  • Root package.json reads 2.5.0 on v2/main
  • No v2.5.0 git tag created by the bump
  • npm run local:gate passes

Activity

  1. added this to the v2.5.0 milestone on Sep 1, 2026
  2. added
    v2Issues and PRs for v2
    choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior change
    on Sep 1, 2026
  3. self-assigned this
    on Sep 1, 2026
  4. linked a pull request that will close this issuechore: bump version to 2.5.0 #2213on Sep 1, 2026
  5. added a commit that references this issue on Sep 1, 2026
    fe35885
  6. cliffhall commented on Sep 1, 2026

    @cliffhall
    MemberAuthor

    Shipped in #2213 (merged as fe35885). v2/main now reads 2.5.0.

  7. changed the title [-]chore: bump version to 2.5.0[/-] [+]Release 2.5.0 step 1: bump version to 2.5.0[/+] on Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changev2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions