Skip to content

v3.59.15 — AGNTCY musl-pin fix, encryption/daemon-config error-message fixes, terminal_history total

Choose a tag to compare

View all tags
@ruvnet ruvnet released this 22 Oct 08:05
· 24 commits to main since this release
v3.59.15
450f653
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new

  • fix(cli): pin @agntcy/slim-bindings to 2.1.1 (#4371, #4377) — 2.0.0-alpha.5's own optionalDependencies claimed a linux-arm64-musl platform package that was never published upstream (confirmed true of every 2.0.0-alpha.*/2.0.0/2.1.0 release). npm silently tolerated this; strict resolvers (mise's aube backend) failed the whole install. 2.1.1 is the earliest release where every platform's optional package actually exists.
  • fix(cli): report actual flag state when decrypting an encrypted store without a key (#3212, #4378) — the decrypt-path error message now reports the real CLAUDE_FLOW_ENCRYPT_AT_REST value and the on-disk RFE1-encrypted state, instead of always claiming the enable flag is set.
  • fix(daemon): read config_set's values envelope in the config.json reader (#3192, #4379) — each config key now resolves independently through scopes.project -> values -> root, so a default-scope config_set daemon.idleSecs 0 call actually takes effect on the running daemon.
  • fix(mcp): report every stored entry in terminal_history's total (#4380) — the combined (no sessionId) history view now reports the real count instead of just the returned page size. 6th instance of the "total computed after pagination slice" bug class.

Verification

  • audit-umbrella-version-lockstep.mjs, leaf-drift check, audit-leaf-versions-published.mjs: all clean.
  • mcp-memory-explicit-dbpath-3196.test.ts, workflow-list-total.test.ts, encryption-vault.test.ts, worker-daemon-resource-thresholds.test.ts, terminal-history-total.test.ts, agntcy-commands.test.ts: 133/133 passing against the built package.
  • All four source PRs went fully green independently before merge; the release PR itself needed one legitimate retry on Supply-chain audit after a transient npm-registry outage on the bulk security-advisories endpoint (confirmed external — main's own CI hit the identical failure at the identical time).

🤖 Generated with RuFlo

Assets 2
Loading