From 5c49dabe0109aad8801fe7a0451b5c8d8bbe02b7 Mon Sep 17 00:00:00 2001 From: Simon Clark Date: Wed, 26 Aug 2026 10:21:21 +0100 Subject: [PATCH] chore(bridge-node): publish 0.17.1 and move the install pin to it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #274's PR B changed the wire contract — `permanent` and `list_orphans` are gone, and the node no longer orphans — but `bridge-node/package.json` was never bumped, so the repo held those changes under the ALREADY-PUBLISHED 0.17.0. npm's 0.17.0 was still the old code. That combination fails quietly rather than loudly: `protocolVersion` is still 2 on both sides, so the handshake passes and nothing refuses. The plugin simply stops sending `permanent: true`, an old node reads it as absent, and removals go on ORPHANING. The #274 behaviour would have been inert on any install that had not rebuilt the node by hand — including jarvis. 0.17.1 published to npm; `DEFAULT_INSTALL_SPEC` moves to it. Publishing is safe ahead of a plugin release because the pin is the gate, not the registry: every released plugin installs its own exact version, so 0.17.1 reaches nobody until a plugin that pins it ships to the Indigo store. 3804 passing, unchanged; bridge-node 673, unchanged. Co-Authored-By: Claude Opus 5 (1M context) --- bridge-node/package-lock.json | 4 ++-- bridge-node/package.json | 2 +- indigo-matter.indigoPlugin/Contents/Info.plist | 2 +- .../Contents/Server Plugin/bridge_agent.py | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/bridge-node/package-lock.json b/bridge-node/package-lock.json index a1d5793..02dcbf1 100644 --- a/bridge-node/package-lock.json +++ b/bridge-node/package-lock.json @@ -1,12 +1,12 @@ { "name": "indigo-matter-bridge", - "version": "0.10.1", + "version": "0.17.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "indigo-matter-bridge", - "version": "0.10.1", + "version": "0.17.1", "license": "MIT", "dependencies": { "@matter/main": "0.17.8", diff --git a/bridge-node/package.json b/bridge-node/package.json index d35cdc0..406c003 100644 --- a/bridge-node/package.json +++ b/bridge-node/package.json @@ -1,6 +1,6 @@ { "name": "indigo-matter-bridge", - "version": "0.17.0", + "version": "0.17.1", "description": "Matter bridge node for the indigo-matter Indigo plugin — exports selected Indigo devices as Matter accessories.", "license": "MIT", "type": "module", diff --git a/indigo-matter.indigoPlugin/Contents/Info.plist b/indigo-matter.indigoPlugin/Contents/Info.plist index 021e9b4..d883c0a 100644 --- a/indigo-matter.indigoPlugin/Contents/Info.plist +++ b/indigo-matter.indigoPlugin/Contents/Info.plist @@ -20,7 +20,7 @@ IwsApiVersion 1.0.0 PluginVersion - 2026.29.1 + 2026.29.2 ServerApiVersion 3.6 diff --git a/indigo-matter.indigoPlugin/Contents/Server Plugin/bridge_agent.py b/indigo-matter.indigoPlugin/Contents/Server Plugin/bridge_agent.py index 68adbd6..7e56df3 100644 --- a/indigo-matter.indigoPlugin/Contents/Server Plugin/bridge_agent.py +++ b/indigo-matter.indigoPlugin/Contents/Server Plugin/bridge_agent.py @@ -63,7 +63,7 @@ #: and matter.js patch releases have changed what Apple Home renders with no code #: change on the bridge side. **This is the one line a release bumps**, in step #: with ``bridge-node/package.json``'s ``version``. -DEFAULT_INSTALL_SPEC = f"{BRIDGE_PACKAGE}@0.17.0" +DEFAULT_INSTALL_SPEC = f"{BRIDGE_PACKAGE}@0.17.1" #: Fallback entry point when the installed package's ``package.json`` is missing #: or unreadable. Must match ``bridge-node/package.json``'s ``main``;