Skip to content

chore(release): bump selat plugin 0.1.9 → 0.1.10; hermes 0.1.3 → 0.1.4 (propagates #106) - #107

Merged
SELAT-DEV merged 1 commit into
mainfrom
chore/bump-plugin-0.1.10
Sep 12, 2026
Merged

SELAT-DEV merged 1 commit into
mainfrom
chore/bump-plugin-0.1.10

Conversation

@SELAT-DEV

Copy link
Copy Markdown
Contributor

Companion to #106. That PR refreshes the pinned runtime; this one is what actually delivers it to existing installs.

Manifest Before After
plugins/selat/.claude-plugin/plugin.json 0.1.9 0.1.10
plugins/selat/.codex-plugin/plugin.json 0.1.9 0.1.10
plugins/selat/.cursor-plugin/plugin.json 0.1.9 0.1.10
plugins/selat-hermes/plugin.yaml 0.1.3 0.1.4

Why this is required

#106 moves the reviewed runtime closure to selat-cli 0.17.1 / selat-discovery 0.25.0 / selat-pay 0.11.0, but the sync workflow touches no plugin manifest — by design, since version bumps are their own PR here (last one: #58).

claude plugin update compares plugin versions only. With the version unchanged it reports "already at the latest version" and short-circuits, so the new pin never reaches an existing install — #106 alone would ship to new installs only. That defeats the propagation runbook that required the selat-cli patch release in the first place.

hermes is bumped for the same reason: #106 also changes plugins/selat-hermes/selat-cli.version and its runtime manifests.

⚠️ Merge order: #106 first, then this

If this merges first, hosts update to 0.1.10 while still carrying the old pin. #106 landing afterwards changes no version, so every existing install stays stuck on the old runtime until the next bump — the exact failure this PR exists to prevent.

What ships once both land

selat-pay 0.11.0 is a breaking release: --prefer-mpp / --prefer-x402 are removed and outbound protocol selection is fully automatic, and the ledger now records detectedProtocol (selat-pay's local detection) instead of implying the rail the router settled on. selat-cli 0.17.1 carries the dependency floor.

Scope

Version strings only — four one-line changes. No runtime, lock, doc, or behaviour changes (those are all in #106). All three JSON manifests re-validated as parseable.

🤖 Generated with Claude Code

The coordinated runtime refresh (#106) moves the pinned runtime to selat-cli
0.17.1 / selat-discovery 0.25.0 / selat-pay 0.11.0, but it touches no plugin
manifest. `claude plugin update` compares plugin versions only, so with the
version unchanged it reports "already at the latest version" and the new pin
never reaches an existing install — the refresh would reach new installs only.

Bumping the manifest version is what actually propagates #106.

hermes is bumped too: #106 also changes plugins/selat-hermes/selat-cli.version
and its runtime manifests.

MERGE ORDER: #106 first, then this. If this merges first, hosts update to
0.1.10 while still carrying the old pin, and #106 landing afterwards changes no
version — leaving every existing install stuck on the old runtime until the
next bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@SELAT-DEV
SELAT-DEV merged commit 5e37c79 into main Sep 12, 2026
SELAT-DEV added a commit that referenced this pull request Sep 12, 2026
…nt pin (#108)

Restamp the vendored discovery driver skill from 0.16.3/0.24.1 to the
reviewed runtime pin (selat-cli 0.17.1 / selat-discovery 0.25.0). Bump
plugins/selat/package.json to 0.1.10 so it matches the harness manifests
after #107.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: SELAT-DEV <SELAT-DEV@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants