@flue/cli
2.3.1 · 18 Nov 2026Apache-2.0217.3k / weekRepositoryHomepagenpmAtom feed
Upgrading @flue/cli From 2.3.0 to 2.3.1
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 2
- fixes
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
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.