chore: bump version to 2.0.0 - #447
Merged
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited), Workspace UI (inherited) Review profile: ASSERTIVE Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
sarve-shreyas
added this pull request to stack #448
September 27, 2026 15:28
…server.json Major bump: the capability registry changes what the server exposes. The five generic registry tools reach 198 Test Management endpoints that previously had no tool at all, and the destructive tier is no longer reachable from this surface — a caller relying on being able to invoke a delete through it will find it withheld rather than refused. server.json's top-level `version` is the manifest's own, not the package's, and stays at 1.0.0; only packages[0].version tracks the npm release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
sarve-shreyas
force-pushed
the
chore/bump-version-2-0-0
branch
from
September 28, 2026 15:20
a321d89 to
1d3c3bf
Compare
gaurav-singh-9227
approved these changes
Sep 28, 2026
sarve-shreyas
added a commit
that referenced
this pull request
Sep 30, 2026
…server.json Re-pointed from 1.6.0. `main` reached 2.0.0 while this sat open (#447), so the old target would have been a DOWNGRADE — and that is what the conflict on this PR was: `package.json` 2.0.0 -> 1.6.0 and `server.json`'s server version 2.0.0 -> 1.0.0. 2.1.0 rather than 2.0.1 or 3.0.0: the change this ships (#445) adds optional `run_id` / `perm_id` / `decision` arguments and loosens `query` from required to optional. Nothing is removed and nothing that worked stops working, so it is a minor. Both `server.json` versions move together, which is how #447 left them.
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.
Stacked on #441. Targets
feat/tm-capability-registry, so it merges with that PR rather than separately.Bumps
1.5.0→2.0.0across the three files a release touches:package.jsonversionpackage-lock.jsonversion(root and the""package entry, which must agree)server.jsonpackages[0].versionserver.json's top-levelversionstays at1.0.0— that is the MCP server manifest's own version, not the package's. Onlypackages[0].versiontracks the npm release, which is what every previous bump onmainchanged.Why major
The capability registry changes what the server exposes, in two ways a consumer can observe:
The second is the breaking half.
Notes
1.5.1onmain. Whichever lands second will need a trivial conflict resolution on the same lines.🤖 Generated with Claude Code