Chore: bump version to 2.1.0 - #446
Merged
Merged
Conversation
MINOR, because the release it names changes how a parked approval is answered
rather than fixing a defect, and a consumer on a caret range picks it up
automatically:
* the resume is ONE request where it was two — the decision POST returns the
run's continuation instead of a 204 followed by a reattach;
* `GET /agent/{run_id}/stream` is no longer used, because with the ask parked
in Atlas's checkpoint there is nothing to reattach to;
* the decision body carries a required `product`.
`npm-publish.yml` is dispatched by hand and publishes whatever this file says,
so MERGE THIS AFTER the change it names. On its own it would ship a 1.6.0 that
is identical to 1.5.1, and the tag would then be wrong for the real one.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
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 |
`package.json` was not the only place the version lives. `package-lock.json` holds it twice (the root entry and `packages[""]`), and `server.json` publishes it to the MCP registry as `packages[0].version` — so a bump that only edits package.json ships a lockfile and a registry entry still claiming 1.5.1. The lockfile change is `npm install --package-lock-only`, not a hand edit. That also corrects one piece of PRE-EXISTING drift it found on the way: the lock recorded `engines.node >= 22` while package.json has said `>= 20.9.0` for some time. Reverting that would mean hand-writing the lock into a state npm does not produce, so it stays. `server.json`'s TOP-LEVEL `version` is deliberately untouched. It has sat at 1.0.0 across every release while the package version moved, so changing it now would be a change of publishing practice rather than part of this bump.
…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.
sarve-shreyas
changed the title
gaurav-singh-9227
approved these changes
Sep 30, 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.
Bumps
@browserstack/mcp-serverto 2.1.0 inpackage.json,package-lock.jsonandserver.json.Ships the version for #445. Merge that first, then this — on its own it publishes a version identical to 2.0.0.
Re-pointed from 1.6.0
mainreached 2.0.0 while this sat open (#447), so the original target would have been a downgrade. That is exactly what the conflict on this PR was:package.jsonserver.json(server version)server.json(npm package)Why 2.1.0 and not 2.0.1 or 3.0.0
#445 adds optional
run_id/perm_id/decisionarguments toaskBrowserStackAIand loosensqueryfrom required to optional. Nothing is removed, and nothing that worked before stops working — so it is a minor, not a patch and not a major.Scope
Five version lines, nothing else — the same shape as #447 and the bumps before it. Both
server.jsonversions move together, which is how #447 left them.