Tags · FailproofAI/failproofai

Repository navigation

v1.0.11

[failproofai-legion-902] Patch the nextjs and mastra-0 fixture adviso…

…ries without moving a pin (#902)

* chore(deps): bump the npm_and_yarn group across 3 directories with 6 updates

Bumps the npm_and_yarn group with 2 updates in the /sdk/typescript/integration/fixtures/ai-4 directory: [ai](https://github.com/vercel/ai/tree/HEAD/packages/ai) and [@ai-sdk/provider-utils](https://github.com/vercel/ai/tree/HEAD/packages/provider-utils).
Bumps the npm_and_yarn group with 2 updates in the /sdk/typescript/integration/fixtures/mastra-0 directory: [ai](https://github.com/vercel/ai/tree/HEAD/packages/ai) and [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk).
Bumps the npm_and_yarn group with 3 updates in the /sdk/typescript/integration/fixtures/nextjs directory: [next](https://github.com/vercel/next.js), [sharp](https://github.com/lovell/sharp) and [source-map-js](https://github.com/7rulnik/source-map-js).


Updates `ai` from 4.3.19 to 5.0.52
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/ai/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/ai@5.0.52/packages/ai)

Updates `@ai-sdk/provider-utils` from 2.2.8 to 3.0.9
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/provider-utils/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/@ai-sdk/provider-utils@3.0.9/packages/provider-utils)

Removes `ai`

Updates `@modelcontextprotocol/sdk` from 1.30.1 to 1.32.1
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](modelcontextprotocol/typescript-sdk@1.30.1...1.32.1)

Updates `next` from 16.3.6 to 16.4.1
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.3.6...v16.4.1)

Updates `sharp` from 0.35.4 to 0.35.5
- [Release notes](https://github.com/lovell/sharp/releases)
- [Commits](lovell/sharp@v0.35.4...v0.35.5)

Updates `source-map-js` from 1.2.1 to 1.2.2
- [Release notes](https://github.com/7rulnik/source-map-js/releases)
- [Changelog](https://github.com/7rulnik/source-map-js/blob/main/CHANGELOG.md)
- [Commits](7rulnik/source-map-js@v1.2.1...v1.2.2)

---
updated-dependencies:
- dependency-name: ai
  dependency-version: 5.0.52
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: "@ai-sdk/provider-utils"
  dependency-version: 3.0.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: ai
  dependency-version:
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@modelcontextprotocol/sdk"
  dependency-version: 1.32.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: next
  dependency-version: 16.4.1
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: sharp
  dependency-version: 0.35.5
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: source-map-js
  dependency-version: 1.2.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>

* [failproofai-legion-902] Keep the fixture pins Dependabot moved; patch the MCP SDK in range

Dependabot's grouped security update moved ai-4 to ai@5.0.52 and mastra-0
to @mastra/core@1.77.0 / @mastra/memory@1.37.1. The mastra-0 tree cannot
install: @mastra/mcp@0.14.5 peers on @mastra/core <0.25.0, so `npm ci`
fails with ERESOLVE in the global setup of every shard that installs it
(frameworks on node 20 and 24, runtimes). Both moves are also the ones
SECURITY.md rules out: those fixtures exist to hold ai 4.x and Mastra 0.x,
and their ai / provider-utils advisories are already recorded there as
accepted.

- ai-4, mastra-0: restored to main.
- mastra-0: @modelcontextprotocol/sdk 1.30.1 -> 1.32.1
  (GHSA-6qxp-vccf-f47h), lockfile only; @mastra/mcp@0.14.5 declares
  ^1.17.5.
- nextjs: ai back to 7.0.111, the ai-7 twin its routes' traces are
  compared against. next 16.4.1, sharp 0.35.5 and source-map-js 1.2.2
  stay; the lockfile differs from main only in those packages.
- Both changelogs record it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JKkzQF2V4WUrot3FaXESPH

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: NiveditJain <nivedit@exosphere.host>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Oct 16, 2026
a6059dd
zip
tar.gz
Notes
Downloads

v1.0.11-beta.4

fix(otel): Claude Code's auth header was refused with 401

Claude Code's settings got OTEL_EXPORTER_OTLP_HEADERS (and the per-signal
LOGS/METRICS copies) as "Authorization=Bearer%20<key>", the spec's encoded
form. Claude Code passes header values through without decoding, so Cloud
received "Authorization: Bearer%20<key>" and refused every log and metric
batch with 401. Write a literal space instead, as Claude Code's own docs do.
Codex was unaffected (its TOML header map holds a plain "Bearer <key>").

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Oct 15, 2026
e7c3adf
zip
tar.gz
Notes
Downloads

v1.0.11-beta.3

chore: bump version to 1.0.11-beta.3

1.0.11-beta.2 is on npm next from before today's two fixes (first-connect
backfill boundary, Done-screen lines); beta.3 carries them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Oct 15, 2026
0e11d77
zip
tar.gz
Notes
Downloads

v1.0.11-beta.2

Merge remote-tracking branch 'origin/feat/tui-ux' into feat/otel

# Conflicts:
#	CHANGELOG.md

Oct 15, 2026
b9ab364
zip
tar.gz
Notes
Downloads

v1.0.11-beta.1

Merge remote-tracking branch 'origin/feat/tui-ux' into feat/otel

# Conflicts:
#	CHANGELOG.md

Oct 12, 2026
5c37ac9
zip
tar.gz
Notes
Downloads

v1.0.11-beta.0

fix(otel): derive each status dot from its own state

Oct 11, 2026
76a749f
zip
tar.gz
Notes
Downloads

v1.0.10

Hermes: instruct runs the call and reminds (no more block-once), load…

… on Hermes 0.20.0 (#875)

* Hermes: instruct runs the call and reminds; load on Hermes 0.20.0

Hermes 0.20.0: the plugin called ctx.get_config and ctx.state, which only
exist from 0.20.1, so register() raised and Hermes loaded it with no hooks.
It now feature-detects both and falls back to Hermes' own config loader and
the same plugin-data directory newer Hermes provides. register() never
raises and registers each hook on its own.

instruct: blocking a correct call once to deliver an instruction made models
treat it as an error, retry with --help, switch to execute_code and give up
unattended runs. The plugin now registers Hermes' tool_execution middleware:
the call runs and the reminder is placed first in its result (first JSON key
failproof_policy_reminder, or a leading line / text block). Calls made by an
execute_code script hand their reminder to the outer result the model reads
and leave the script's copy untouched. The pre_llm_call protocol note tells
the model a reminder is an operator rule, never to be quoted to the user.
deny still blocks. Without the middleware, instruct holds the call once,
keyed by policy rather than tool.

Hardening: no hook raises (pre_tool_call blocks on internal errors), one
deadline for connect+send+read capped at 25 s, observers wait at most 2 s,
a reminder is attached once per session and turn and compacted on large
results, heartbeat.json records what a running Hermes loaded, Hermes 0.21's
renamed process_manage/cronjob_manage/todo_list tools are canonicalised, and
plugin.yaml carries the package version.

OSV-Scanner: ignore GHSA-vfj7-8cjw-p6xm (braces 3.0.3, no fixed version,
dev-only via @next/eslint-plugin-next), re-review by 2026-11-20.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Hermes plugin: never merge a tool's own failproof_policy_reminder into ours

The protocol note tells the model failproof_policy_reminder is an operator
rule. When a tool's JSON result already carried that key and an instruct
policy fired, its value was appended to the plugin's reminder, presenting
tool output as operator text. The tool's value now moves to
tool_failproof_policy_reminder and the reminder holds only the plugin's own
text. Regression test included.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Version 1.0.10-beta.1 for this branch's beta

main and another branch already carry 1.0.10-beta.0. A machine holding a
different build's ~/.failproofai/bin/failproofaid-1.0.10-beta.0 would reuse
that daemon (ensureFailproofaidBinary returns an existing versioned binary),
so this beta gets its own number. This PR's CHANGELOG entries move under it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Hermes plugin: expire handoffs on read, claim reminders atomically, bound the compact reminder; 1.0.10 notes

- A reminder handed off to a script's inner call now expires 60 s after it was
queued even when nothing else is queued, and an allow or deny verdict for the
same call drops a handoff an earlier, blocked identical call left behind.
- Reminders are claimed for a session + turn in one locked step, so two calls
running in parallel cannot both attach the same one.
- The compact reminder caps each policy name (80 chars), each reason (160) and
the number of reminders (3, then "+N more"), so its size is bounded.
- Docs: Hermes saves a result past 15% of the model's context window
(8,000-100,000 chars, read_file never); 8,000 is only the floor. The reminder
is always attached, also on a result just under that floor.
- CHANGELOG: a 1.0.10 section for the stable release, with the Hermes action
needed (instruct no longer stops an action; use deny).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Oct 5, 2026
7b3655a
zip
tar.gz
Notes
Downloads

v1.0.10-beta.1

Version 1.0.10-beta.1 for this branch's beta

main and another branch already carry 1.0.10-beta.0. A machine holding a
different build's ~/.failproofai/bin/failproofaid-1.0.10-beta.0 would reuse
that daemon (ensureFailproofaidBinary returns an existing versioned binary),
so this beta gets its own number. This PR's CHANGELOG entries move under it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Oct 5, 2026
dba4c19
zip
tar.gz
Notes
Downloads

PreviousNext

Navigation Menu

Repository navigation

v1.0.11

ts-sdk-v0.0.1-beta.1

failproofai-sdk-v0.0.1b6

v1.0.11-beta.4

v1.0.11-beta.3

v1.0.11-beta.2

v1.0.11-beta.1

v1.0.11-beta.0

v1.0.10

v1.0.10-beta.1

Tags: FailproofAI/failproofai