Packages

@flue/opentelemetry

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

Upgrading @flue/opentelemetry From 0.8.1 to 0.9.0

1 release in betweenevery note read

Other targets from 0.8.1Newest 0.x0.11.1Latest2.3.1
  1. 0.8.1yours
  2. 0.9.0target

Before you upgrade

Tick each one off as you go
  • Breaking0.9.0
  • Breaking0.9.0
  • Breaking0.9.0
  • Breaking0.9.0
  • Breaking0.9.0
  • Breaking0.9.0
  • Breaking0.9.0

Release by release

  1. 0.9.0

    Migration needed2 Jun 20266 new · 9 fixes
    • Breaking

      Move application routing imports out of @flue/runtime/app. Import flue, admin, and Fetchable from @flue/runtime/routing. Import provider APIs and observe from @flue/runtime, and Workers AI binding types from @flue/runtime/cloudflare. Rename the ProviderSettings type to ProviderConfiguration.

    • Breaking

      Check your authored source directory. Flue now selects exactly one source directory in priority order: .flue/, src/, then the project root. If your project already has a src/ directory, move root-level agents and workflows into the selected source directory so Flue continues to discover them.

    • Breaking

      Cloudflare: Own Cloudflare Durable Object migrations in your project Wrangler config. Flue still generates classes and bindings, but no longer appends migrations automatically. Before upgrading an existing deployment, copy its complete ordered flue-class-* migration history from the previously generated .flue-vite.wrangler.jsonc or built wrangler.json into the project-root Wrangler config. Keep deployed tags unchanged, and append a uniquely tagged new_sqlite_classes entry whenever you add an agent or workflow class.

    • Breaking

      Workflows: Retry interrupted Cloudflare workflows explicitly. Flue no longer starts a replacement workflow run automatically after an interruption. The interrupted run is recorded as failed; invoke the workflow again when retrying is appropriate. Restart-link fields and their legacy OpenTelemetry attributes were removed.

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.