0.15.21: version bump Tree-equivalent to v0.15.20 (preceded by the revert commit). Bumping to 0.15.21 sets the package up for normal patch releases on the 0.15.x line going forward — no version-number collisions with the unpublished 0.16/0.17 work.
Tianren Dong tianrendong.dtr@gmail.com
Sat, 16 May 2026 13:14:10 -0400
3 files changed,
9 insertions(+),
2 deletions(-)
M
CHANGELOG.md
→
CHANGELOG.md
@@ -2,6 +2,13 @@ # Changelog
All notable user-facing changes to `pi-chrome`. +## 0.15.21 — 2026-05-16 + +### Reverted 0.16.x and 0.17.x lines + +- Versions 0.16.0 through 0.17.2 were published to npm and subsequently unpublished. 0.17.3 was prepared locally but never published. The work introduced in those versions — mandatory pairing, signed-envelope auth, standalone bridge daemon, idempotent onboard, etc. — is reachable only via git tags (`v0.16.0` … `v0.17.3`) and is not in the current main branch. +- This release is **tree-equivalent to 0.15.20** with a version-only bump so future patch releases can ship cleanly. + ## 0.15.20 — 2026-05-15 - **Interruptible `chrome_*` tools.** All `chrome_*` tools now honor the agent harness `AbortSignal`, so pressing Esc aborts in-flight bridge calls (including the long-polling `chrome_wait_for`) immediately instead of waiting out the full `timeoutMs`.
M
extensions/chrome-profile-bridge/browser-extension/manifest.json
→
extensions/chrome-profile-bridge/browser-extension/manifest.json
@@ -1,7 +1,7 @@
{ "manifest_version": 3, "name": "Pi Chrome Connector", - "version": "0.15.20", + "version": "0.15.21", "description": "Lets Pi control tabs in Chrome via a local connector at 127.0.0.1.", "permissions": [ "tabs",
M
package.json
→
package.json
@@ -1,6 +1,6 @@
{ "name": "pi-chrome", - "version": "0.15.20", + "version": "0.15.21", "scripts": { "version": "node scripts/sync-manifest-version.js", "prepublishOnly": "node scripts/sync-manifest-version.js"