From 4c4a8bf72b166d10135af81c59aac4bbda8678a9 Mon Sep 17 00:00:00 2001 From: Shreyas Sarve Date: Sun, 27 Sep 2026 20:35:02 +0530 Subject: [PATCH 1/2] Chore: bump version to 1.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 362f46ba..52461d6d 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@browserstack/mcp-server", - "version": "1.5.1", + "version": "1.6.0", "description": "BrowserStack's Official MCP Server", "mcpName": "io.github.browserstack/mcp-server", "main": "dist/index.js", From c35e3062d893eb537815b9032de7df9d9fcad2d1 Mon Sep 17 00:00:00 2001 From: Shreyas Sarve Date: Mon, 28 Sep 2026 12:43:18 +0530 Subject: [PATCH 2/2] Carry the bump into the lockfile and the registry manifest MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `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. --- package-lock.json | 6 +++--- server.json | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/package-lock.json b/package-lock.json index 6119a5bb..28490f9a 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@browserstack/mcp-server", - "version": "1.5.1", + "version": "1.6.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@browserstack/mcp-server", - "version": "1.5.1", + "version": "1.6.0", "license": "ISC", "dependencies": { "@modelcontextprotocol/sdk": "^1.29.0", @@ -40,7 +40,7 @@ "vitest": "^4.0.16" }, "engines": { - "node": ">=22" + "node": ">=20.9.0" } }, "node_modules/@emnapi/runtime": { diff --git a/server.json b/server.json index 28cb9ab0..38668de0 100644 --- a/server.json +++ b/server.json @@ -11,7 +11,7 @@ { "registryType": "npm", "identifier": "@browserstack/mcp-server", - "version": "1.5.1", + "version": "1.6.0", "transport": { "type": "stdio" },