chore: refresh SELAT runtime (0.16.16 / 0.24.9 / 0.9.14) - #100
Merged
Conversation
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.
This PR was generated from the coordinated SELAT runtime release gate.
@selat-ai/selat-cli0.16.16@selat-ai/selat-discovery0.24.9@selat-ai/selat-pay0.9.14The workflow regenerated
selat-runtime-package.jsonand its npm lockfilewith lifecycle scripts disabled, resynced the documented no-plugin pin in
README.md,install.md, andguides/*.md, then validated direct versions,npm integrity metadata, the
ws@8.21.0override, the SessionStartinstaller's
npm ci --ignore-scriptscontract, byte-identical vendoredcopies in
plugins/selat-hermes/(subdirectory install), and that no docstill names a superseded CLI version.
Generated by
Prepare coordinated SELAT runtime release.