@flue/opentelemetry
2.3.1 · 18 Nov 2026Apache-2.0147.1k / weekRepositoryHomepagenpmAtom feed
Upgrading @flue/opentelemetry From 0.9.2 to 2.3.1
21 releases in betweenevery note read
- 43
- changes to make
- 0
- advisories fixed
- 29
- new
- 84
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
Release by release
- Fixed
Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 1.5.2, fixing builds that picked up pi-ai 1.5.@flue/runtime2.3.0 imported TypeBox through@earendil-works/pi-ai, which stopped re-exporting it in 1.5.0, so a fresh install failedvite build. Flue now depends ontypeboxdirectly and requires pi^1.5.0; remove any overrides that held pi at 1.4. If your own code importsTypeorStaticfrom@earendil-works/pi-ai, import them fromtypeboxinstead. Pi now validates tool arguments with its own JSON Schema validator, which coerces a little more (for example"3"for a number) and words its validation errors differently. OpenAI-compatible requests with no tools no longer send"tools":; setcompat.requiresToolsWithToolHistory: trueon models behind proxies that require it, such as older LiteLLM versions in front of Anthropic. - Fixed
Workers AI binding models on the Responses API declare tools the way pi's own OpenAI provider does. Since pi 1.4, the binding passed a boolean where pi expected a tool-support mode, so a model without deferred tool loading could leave tools added mid-conversation out of its request. Models that support mid-conversation tool additions now declare every tool through
additional_toolsinput items.
- Fixed
- New
Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 1.1.0. New models resolve with no configuration, including Claude Sonnet 5.5 (anthropic/claude-sonnet-5-5), Claude Haiku 5.5 (anthropic/claude-haiku-5-5), and GPT-6.1 Sol (openai/gpt-6.1-sol). Azure users must update: Pi renamed the Azure provider fromazure-openai-responsestoazure, so changeazure-openai-responses/...model specifiers andprovidersconfig entries toazure. TheAZURE_OPENAI_*environment variables are unchanged. Tool and turndurationMsvalues now come from Pi's monotonic timing, so a tool's duration covers only its execution, not Flue's hooks or result storage. - Fixed
useAgentFinishcallbacks once again see state written during the response. Since 2.2.0, finish hooks ran against the agent render from before the response's final turn, so a durable guard set by a finish callback — the documentedusePersistentStatepattern for appending a reminder once — was never observed: the callback re-appended on every cycle until the response failed at the runaway-loop ceiling. The agent now re-renders before each finish-hook cycle (#818). - Fixed
read_skill_resourceaccepts a packaged skill path without its leading/. Models often echo the advertised/.flue/packaged-skills/...path without the slash, and the read failed as not found (#781). - Fixed
The local sandbox SIGKILLs a command's whole process group after the grace period, even when the shell exits first. On an
exec()timeout or abort, the pending SIGKILL was cancelled once the shell's pipes closed, so a process that ignored SIGTERM and held none of the shell's output kept running afterexec()returned (#809). - Fixed
Execution interceptors see
agentNameon model, tool, and shell steps, not only on the outeragentoperation. The root harness's execution context carried only the instance id, so an interceptor that branches per agent took its default branch on every step (#785). - Fixed
flue init --target cloudflarescaffolds the Workers AI binding that keylesscloudflare/...models need, commented out inwrangler.jsonc. The generated agent suggested switching to a keyless Cloudflare model but nothing declaredenv.AI; it now points at the binding to uncomment. The binding stays off by default because it reaches your Cloudflare account even in local dev (#739). - Fixed
The E2B sandbox blueprint returns a non-zero exit from
exec()instead of throwing. E2B'scommands.run()throwsCommandExitErroron a non-zero exit, so a failing command rejected with no command or stderr instead of resolving with itsexitCode. The blueprint is bumped to version 2; runflue update sandbox e2bto update an existing integration (#805).
- New
2.2.0 – 2.2.23 releases, nothing new or fixed in the notes
- Fixed
Record tool arguments and results of every payload shape on the standard
gen_ai.tool.call.arguments/gen_ai.tool.call.resultattributes, so OTel backends can display them. The shape-based diversion to the vendorflue.tool.call.*fallback keys is removed — those keys are no longer emitted, and their constants are retained for source compatibility. Payloads record exactly as before: objects/arrays as JSON strings, strings byte-for-byte within the content budget, other scalars as their JSON form.
- Fixed
- New
Trace content budgets are now configurable.
createCloudflareTracing({ contentBudgetBytes })andcreateOpenTelemetryInstrumentation({ contentBudgetBytes })override the default 56 KiB per-span content pool — raise it (e.g.contentBudgetBytes: 200_000) to ship fuller prompts and tool results to an observability backend that isn't bound by workerd's 64 KiB span-attribute cap, or tighten it. The 128-byte sentinel floor and the shared-pool semantics are unchanged. - Fixed
An invalid
contentBudgetBytesvalue (non-integer, too small, or too large) now throws aTypeErrorat setup instead of producing confusing trace content later. - Fixed
The span that records conversation compaction now honors the configured budget, so its content is truncated or shipped consistently with every other span.
- New
2.0.7 – 2.0.82 releases, nothing new or fixed in the notes
- Fixed
Published packages once again include the bundled Flue documentation. The 2.0.4 and 2.0.5 releases omitted the generated
docs/directories from@flue/cli,@flue/runtime, and@flue/sdk, causing commands such asflue docs read guide/sandboxesto fail.
- Fixed
- Fixed
Published packages once again resolve internal Flue dependencies to the release version. The 2.0.4 release accidentally shipped raw pnpm
workspace:dependency specifiers, making affected packages impossible to install outside the workspace. The complete lockstep package set is republished as 2.0.5 through pnpm so every internal dependency resolves to 2.0.5 (#657).
- Fixed
8 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.