@flue/runtime
2.3.1 · 18 Nov 2026Apache-2.0524.4k / weekRepositoryHomepagenpmAtom feed
Upgrading @flue/runtime From 0.7.1 to 0.8.0
1 release in betweenevery note read
- 5
- changes to make
- 0
- advisories fixed
- 5
- new
- 2
- fixes
Before you upgrade
Tick each one off as you go- Breaking0.8.0
- Breaking0.8.0
- Breaking0.8.0
- Breaking0.8.0
- Breaking0.8.0
Release by release
- Breaking
Applications must adopt the agent/workflow split. Move one-shot request/result modules from
agents/toworkflows/; long-lived agent modules now default-exportcreateAgent(...). Workflows create harnesses withinit(agent)rather than inlineinit({ ... })configuration. - Breaking
Routing and run semantics changed. Public HTTP and WebSocket exposure is declared through
routeandwebsocketmiddleware exports. Runs,/runs, andflue logsnow describe workflows only; direct or dispatched agent interactions correlate by instance, session, operation, anddispatchIdinstead ofrunId. - Breaking
Roles and older agent definitions were replaced. Migrate roles and
task({ role })to nameddefineAgentProfile(...)subagents andtask({ agent }); migrate reusable agent definitions to profiles andToolDefimports toToolDefinition. - Breaking
Build and Cloudflare configuration changed. Node and Cloudflare builds now use a shared Vite graph; Cloudflare development follows
.dev.vars/.envandCLOUDFLARE_ENVconventions. Cloudflare workflows now receive per-workflow Durable Object bindings, so review generated Wrangler configuration when upgrading.
- Breaking
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.