Skip to content

chore: refresh SELAT runtime (0.17.1 / 0.25.0 / 0.11.0) - #106

Merged
SELAT-DEV merged 1 commit into
mainfrom
ci/selat-runtime-0.17.1-0.25.0-0.11.0
Sep 12, 2026
Merged

SELAT-DEV merged 1 commit into
mainfrom
ci/selat-runtime-0.17.1-0.25.0-0.11.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR was generated from the coordinated SELAT runtime release gate.

Component Exact version
@selat-ai/selat-cli 0.17.1
@selat-ai/selat-discovery 0.25.0
@selat-ai/selat-pay 0.11.0

The workflow regenerated selat-runtime-package.json and its npm lockfile
with lifecycle scripts disabled, resynced the documented no-plugin pin in
README.md, install.md, and guides/*.md, then validated direct versions,
npm integrity metadata, the ws@8.21.0 override, the SessionStart
installer's npm ci --ignore-scripts contract, byte-identical vendored
copies in plugins/selat-hermes/ (subdirectory install), and that no doc
still names a superseded CLI version.

Review and merge this PR only after the component release notes and
cross-repository compatibility checks have been approved. Merging changes
the runtime installed by every SELAT plugin SessionStart hook.

Generated by Prepare coordinated SELAT runtime release.

@SELAT-DEV

Copy link
Copy Markdown
Contributor

Companion version bump: #107 (selat 0.1.9 → 0.1.10, hermes 0.1.3 → 0.1.4).

Merge this PR first, then #107. This one refreshes the pinned runtime but touches no plugin manifest, and claude plugin update compares plugin versions only — so on its own it reaches new installs only. #107 is what propagates it to existing ones.

If #107 merged first, hosts would update while still carrying the old pin, and this PR landing afterwards would change no version — leaving existing installs stuck until the next bump.

@SELAT-DEV
SELAT-DEV merged commit 25f1d63 into main Sep 12, 2026
1 check passed
SELAT-DEV added a commit that referenced this pull request Sep 12, 2026
…1.4 (#107)

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: Karen Sheng <ksherlocked@gmail.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.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.

1 participant