@inline-chat/hermes-agent-adapter 0.0.7 → 0.0.8-alpha.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -81,7 +81,7 @@ Set up the Inline Hermes Agent adapter on this machine.
81
81
  Constraints:
82
82
  - Do not read, print, or edit .env files.
83
83
  - Do not print Inline tokens or other secrets.
84
- - Use an Inline token from INLINE_TOKEN or INLINE_BOT_TOKEN; if neither is present, stop and point me to https://inline.chat/docs/creating-a-bot.
84
+ - Use an Inline token from INLINE_TOKEN or INLINE_BOT_TOKEN when already available; otherwise use Hermes's guided setup without exposing the token.
85
85
 
86
86
  Tasks:
87
87
  1. Verify Node.js is version 20 or newer and Hermes Agent is installed.
@@ -146,7 +146,7 @@ uv run ./hermes plugins list --plain --no-bundled
146
146
  Expected local output includes:
147
147
 
148
148
  ```text
149
- enabled user 0.0.7 inline-platform
149
+ enabled user 0.0.8-alpha.0 inline-platform
150
150
  ```
151
151
 
152
152
  ## Update Or Reinstall
@@ -169,7 +169,7 @@ mismatch, rerun the same command after rebuilding or upgrading the package.
169
169
 
170
170
  - Hermes Agent: requires the external user plugin registry and native platform
171
171
  plugin loader available in Hermes Agent `0.17.x`. This package was validated
172
- against Hermes Agent `0.19.1` from source commit `cc4cab2`.
172
+ against Hermes Agent `0.20.0` from source commit `3c27eb6`.
173
173
  - Node.js: `>=20` is required for the bundled sidecar. Hermes-managed Node 22,
174
174
  system Node, or an explicit `INLINE_NODE_BIN` path all work.
175
175
  - Inline transport: the sidecar uses `@inline-chat/realtime-sdk@0.0.14` and is
@@ -191,10 +191,10 @@ Before publishing, run:
191
191
  bun run release:preflight
192
192
  ```
193
193
 
194
- This runs `npm publish --dry-run --access public`. npm invokes
195
- `prepublishOnly`, so the dry-run must pass `bun run check`, rebuild the packed
196
- runtime files, verify the shipped `inline-hermes` binary, and print the final
197
- tarball contents without publishing.
194
+ This creates an isolated registry-dependency stage, runs the full package
195
+ check, packs one read-only tarball, and runs `npm publish --dry-run` against
196
+ those exact bytes. It prints the artifact path, SHA-256, and file list so the
197
+ trusted-publishing workflow can hash-check and publish the same artifact.
198
198
 
199
199
  Maintainers should also run the manual live-test and publish checklist in
200
200
  [`hermes-agent/RELEASE.md`](https://github.com/inline-chat/inline/blob/main/hermes-agent/RELEASE.md).