Repository navigation
v0.4.0
llm-translator v0.4.0 Changelog
Release Date: November 2026
Release Type: Minor
Branch: next → master
Overview
Version 0.4.0 lets the translator know which reasoning efforts each model honours, and lets an alias pin effort and thinking, so one local model can sit behind Claude Code's model tiers at different depths. It also maps the non-standard finish reasons some servers send, makes the tool-error marker configurable (with opt-in inference in the other direction), and takes the keep-alive interval from the upstream a request goes to.
The Node.js floor drops from 24 to 22.15. Nothing is removed and every existing config keeps working; the one behaviour change to look at is that fatal finish reasons now surface as errors instead of an apparently finished answer.
✨ Features
Per-model effort levels and aliases that pin effort and thinking (#99)
A new efforts config key lists the levels a model honours, by model name after aliases: a list such as ["low", "high", "max"], or { "levels": [...], "default": ... }. For a listed model on an OpenAI-protocol upstream, a listed effort is sent unchanged and any other snaps to the nearest listed level (a tie goes to the higher one) with a warning. A request with no effort gets the model's default: a level, null to send nothing, or by default the listed level nearest medium. The vLLM driver's max/xhigh → high clamp and the medium default no longer apply to listed models; models without a list behave as before.
An alias can now be { "model": "...", "effort": "max", "thinking": false } as well as a plain string. Pinned values override the request's, and the effort still goes through the model's list. GET /v1/models lists aliases (alias_of) and adds efforts, default_effort, effort and thinking to the entries they apply to, in both the Anthropic and OpenAI shapes. Resolves #80, resolves #81; the reasoning is in D-48 in docs/decisions.md.
Non-standard finish reasons (#102)
Finish reasons outside OpenAI's set used to all become end_turn. Now model_length maps to max_tokens, eos and eos_token to end_turn, and abort, aborted, error and insufficient_system_resource to an error: a single error event in a stream, or a 502 (503 for insufficient_system_resource) for a non-streaming reply. Resolves #27.
Configurable tool error marker and is_error inference (#103)
toolErrorMarker (default "[error] ") sets the text toolErrors puts in front of a failed tool result. The new toolErrorInference setting (off by default) works the other way: an OpenAI tool message whose text starts with the marker becomes a tool_result with is_error: true, with the marker removed. toolErrors stays off by default for every driver. Resolves #58.
Per-upstream pingInterval (#104)
The server now takes pingInterval from the routed upstream's settings, over the global value as for every other setting, and uses it for the early-commit wait as well as the keep-alives. In a round robin pool it is the member the request goes to; a failover to another member keeps the first member's interval. Resolves #55.
🔧 Compatibility
Node.js 22.15 floor (#105)
engines.node is now >=22.15.0 (was >=24.0.0), and the build targets node22. unpdf 2 declares Node.js 24, but nothing the translator calls in it needs 24: PDF.js polyfills the newer built-ins on 22 and 24, and the one it doesn't is only reached by XFA images and the viewer's signature editor. npm prints an engine warning for unpdf on Node.js 22; text extraction and page rendering work. Node.js 26 is the fastest. Developing the package needs Node.js 22.22 (devEngines), and CI's minimum matrix version follows it.
🔧 CI & tooling
- The tests set the
llm-translator-devcondition withdevCondition()from@cldmv/configs(#100). The oldtest.nodeOptionsentry is not a Vitest option and did nothing; the resolve and SSR conditions it sat next to are now set by the same helper, along withtest.execArgvfor the workers.
📚 Documentation
- NEW: docs/changelog/v0/v0.4.0.md: this changelog.
- docs/settings.md, docs/server.md, docs/drivers.md and docs/protocol-support.md cover the new settings and config keys; the feature inventory and known limitations are updated to match.
🔧 Dependencies
- Dev only:
@cldmv/configs^1.3.0 → ^1.4.0, fordevCondition()(#100).
Upgrade notes
- No config changes are needed; string aliases and models without an
effortslist behave as before. - A response that ends with
abort,aborted,errororinsufficient_system_resourceis now an error rather than a normalend_turnmessage. Clients that retried on errors will now retry these too. - Node.js 22.15 or newer is enough to run the package.
| Metric | Coverage |
|---|---|
| Statements | 100.0% |
| Branches | 100.0% |
| Functions | 100.0% |
| Lines | 100.0% |
Avg: 100.0% · d69c427 · Node lts/*