hermes: release authorization and recovery fixes as 0.0.21 - #107
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 59337a9f9f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "name": "@inline-chat/hermes-agent-adapter", | ||
| "version": "0.0.20", | ||
| "version": "0.0.21", |
There was a problem hiding this comment.
Require 0.0.21 from the managed Hermes installer
inline agents setup --target hermes will continue to keep an existing 0.0.20 plugin: MINIMUM_HERMES_PLUGIN_VERSION remains 0.0.20, and ensure_plugin returns early for any live plugin at or above that floor. Consequently, users who installed the previous release and rerun the normal setup/repair flow never invoke the npm exec ... install --force path and remain on the version without the authorization and inbound-recovery fixes this release is meant to deliver. Raise the CLI floor (and its associated assertions) to 0.0.21 so the managed path upgrades them.
Useful? React with 👍 / 👎.
Publishes the merged native authorization and inbound recovery fixes as
@inline-chat/hermes-agent-adapter@0.0.21, so npm users can receive the same fixes as the reviewed catalog source. Updates package/manifest/lock versions, the diagnostic user agent, examples and version assertions. No runtime behavior changes beyond the diagnostic version string.Validation: isolated registry-dependency release preflight passes typecheck, lint, all85tests, tracked sidecar byte parity and exact-tarball npm dry run. Independent subagent reviewed the complete version diff and found no issues. Trusted publishing will revalidate its immutable artifact against Hermes and the Umbrel image before publishing; registry install verification follows publication.