Packages

@flue/postgres

2.3.1 · 18 Nov 2026Apache-2.073.3k / weekRepositoryHomepagenpmAtom feed

Upgrading @flue/postgres From 2.0.0 to 2.3.1

15 releases in betweenevery note read

  1. 2.0.0yours
  2. 14 releases
  3. 2.3.1target
  4. 4 pre
0
changes to make
0
advisories fixed
1
new
19
fixes

Release by release

  1. 2.3.1

    18 Nov 20262 fixes
    • Fixed

      Updated @earendil-works/pi-ai and @earendil-works/pi-agent-core to 1.5.2, fixing builds that picked up pi-ai 1.5. @flue/runtime 2.3.0 imported TypeBox through @earendil-works/pi-ai, which stopped re-exporting it in 1.5.0, so a fresh install failed vite build. Flue now depends on typebox directly and requires pi ^1.5.0; remove any overrides that held pi at 1.4. If your own code imports Type or Static from @earendil-works/pi-ai, import them from typebox instead. 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":; set compat.requiresToolsWithToolHistory: true on 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_tools input items.

  2. 2.3.0

    12 Oct 20261 new · 6 fixes
    • New

      Updated @earendil-works/pi-ai and @earendil-works/pi-agent-core to 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 from azure-openai-responses to azure, so change azure-openai-responses/... model specifiers and providers config entries to azure. The AZURE_OPENAI_* environment variables are unchanged. Tool and turn durationMs values now come from Pi's monotonic timing, so a tool's duration covers only its execution, not Flue's hooks or result storage.

    • Fixed

      useAgentFinish callbacks 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 documented usePersistentState pattern 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_resource accepts 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 after exec() returned (#809).

    • Fixed

      Execution interceptors see agentName on model, tool, and shell steps, not only on the outer agent operation. 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 cloudflare scaffolds the Workers AI binding that keyless cloudflare/... models need, commented out in wrangler.jsonc. The generated agent suggested switching to a keyless Cloudflare model but nothing declared env.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's commands.run() throws CommandExitError on a non-zero exit, so a failing command rejected with no command or stderr instead of resolving with its exitCode. The blueprint is bumped to version 2; run flue update sandbox e2b to update an existing integration (#805).

  3. 2.0.7 – 2.2.27 releases, nothing new or fixed in the notes

  4. 2.0.6

    14 Sep 20261 fix
    • 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 as flue docs read guide/sandboxes to fail.

  5. 2.0.5

    11 Sep 20261 fix
    • 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).

  6. 2.0.4

    9 Sep 20261 fix
    • Fixed

      "Connection error." is now classified as a retryable model error. The retryable-error matcher recognized connection reset/connection refused/connection lost but not a bare connection error — a transient "Connection error." (with its trailing period) fell through the pattern and terminated the submission as a hard failure. The matcher now also accepts connection error and the run retries it under the transient-error budget (#629).

  7. 2.0.3

    5 Aug 20261 fix
    • Fixed

      The Cloudflare Agents SDK (agents) is now a dependency of @flue/vite — projects no longer declare it. The generated Worker entry is the only code that imports the SDK, so the package that generates it ships it, and every project runs the SDK version Flue was tested against instead of whatever a scaffolded range resolves to on install day; flue init --target cloudflare stops writing the dependency, and existing projects can delete theirs. A project that declares its own agents dependency still wins — the plugin only falls back to its bundled copy when the project's node_modules chain has none. This also unbreaks fresh installs, which failed on an ai peer conflict internal to agents@0.14.5, the newest version the scaffolded ^0.14.2 range had come to resolve (reported by Ben Buzbee). The scaffolded wrangler range moves to ^4.113.0.

  8. 2.0.2

    4 Aug 20265 fixes
    • Fixed

      Conditional tool additions are now cache-safe on models with deferred tool loading. A tool mounted by the rerender that follows a settled tool batch is anchored to that batch's final tool result, so current first-party Anthropic models (Claude 4.5 and later, excluding Haiku) keep the added definition out of the cached prompt prefix instead of invalidating it; other providers ignore the anchor and their requests are unchanged. The anchor persists with the run and is restored on rehydration, so a rehydrated context matches the live loop exactly (the internal reduced-state format counter bumps to 2). The Tools guide now states the actual cache contract: tool-set changes rewrite the native tools array and invalidate the provider prompt cache, except additions unlocked by a completed tool call on the models above (#545).

    • Fixed

      The cloudflare-shell blueprint is replaced by cloudflare-computer, built on @cloudflare/computer — the successor to @cloudflare/shell that hosts a durable SQLite-backed workspace in the agent's own Durable Object with a just-bash shell backend, and can escalate to a container backend where a JavaScript shell isn't enough. The adapter provides a real exec() and keeps the framework's standard tool set instead of substituting a code tool. flue add cloudflare-shell and the old docs URLs redirect to the successor.

    • Fixed

      Cloudflare trace spans whose terminal event never arrives (their operation orphaned by deadline force-settlement or recovery) are force-closed when the submission settles, so the run's invoke_agent root span no longer vanishes from the trace. Forced closes carry a flue.span.forced_close attribute, and span-close failures are reported instead of swallowed.

    • Fixed

      The sandbox types are renamed to match their roles; the old names remain as deprecated aliases. SessionEnv → Sandbox (the live environment handle behind harness.sandbox and the standard tools), SandboxApi → SandboxDriver (the per-provider interface a sandbox adapter implements), createSandboxSessionEnv() → sandboxFromDriver(), SessionToolFactory/SessionToolFactoryOptions → SandboxToolFactory/SandboxToolFactoryOptions, and SandboxFactory.createSessionEnv() → createSandbox(). No action is required: the old type names and createSandboxSessionEnv are exported as deprecated aliases, and a factory implementing only the legacy createSessionEnv() method still initializes (with a one-time deprecation warning). Blueprints, examples, and docs emit the new names.

    • Fixed

      New docs reference page: Agent Behavior — the out-of-the-box runtime contract in one place: the built-in tools' parameters and truncation limits, environment defaults, message admission and turn-boundary joining, context composition and compaction, and the enforced limits.

7 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.