chore(bridge-node): publish 0.17.1 and move the install pin to it - #316
Merged
Conversation
#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) <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
The problem this fixes
#274's PR B changed the wire contract —
permanentandlist_orphansgone, node no longer orphans — butbridge-node/package.jsonwas never bumped. The repo held those changes under the already-published0.17.0, while npm's0.17.0was still the old code.It fails quietly, which is worse than failing loudly.
protocolVersionis still2on both sides, so the handshake passes and nothing refuses. The plugin just stops sendingpermanent: true, an old node reads it as absent, and removals go on orphaning.The #274 behaviour would have been inert on any install that hadn't rebuilt the node by hand — including jarvis. I caught it while checking version skew before deploying, not from a failing test.
What changed
indigo-matter-bridge@0.17.1published to npm (673 tests green, build clean)DEFAULT_INSTALL_SPECmoves0.17.0→0.17.1Why publishing ahead of a plugin release is safe
The pin is the gate, not the registry. Every released plugin installs its own exact version, so
0.17.1sits unused until a plugin release that pins it ships to the Indigo store. Existing installs keep resolving0.17.0and are unaffected.Numbers
3804 passing, unchanged. bridge-node 673, unchanged.
Version 2026.29.2. No
[release]marker.🤖 Generated with Claude Code