v0.15.0
Version v0.15.0, dated October 5, 2026, is a security and resilience release with the fixes from a dual-model code review. It contains one breaking change: the Anthropic and Ollama header overrides now require allowHeaderOverride=true. Read Upgrade notes before upgrading.
Upgrade
Upgrade the core and each optional module you use together:
Every component and observability module at v0.15.0 requires core v0.15.0.
Upgrade notes
Anthropic and Ollama header overrides (breaking): the
AnthropicSystem,AnthropicModel,AnthropicMaxTokensandAnthropicTemperatureheaders, and theOllamaModelandOllamaSystemheaders, are now ignored unless the endpoint setsallowHeaderOverride=true. To keep the old behaviour, add the option to the endpoint URI, only where the headers cannot be influenced by untrusted input:MongoDB
find: afindwithout a limit returns at most 10000 documents. RaisemaxResults(0= unlimited) or page withCamelMongoDbLimit/CamelMongoDbSkip.exec: stdout and stderr are each capped at 32 MiB; check
CamelExecOutputTruncatedor raisemaxOutputSize.File consumer: at most 100000 ingested files are remembered to skip duplicate events. A long-evicted file that is touched again may be ingested again; raise
maxSeenEntriesif needed.
Security
- Anthropic and Ollama: header overrides are gated by
allowHeaderOverride, like every other component. On a route fed by untrusted input, they let a sender replace the system prompt (prompt injection) or pick the model and token budget (cost).
Fixed
Consumer resilience
- NATS: a subscription error other than a timeout no longer ends the consumer while the route still appears started. The consumer backs off, reconnects or resubscribes, and only exits when its context is cancelled.
- STOMP: a read error or broker
ERRORframe no longer ends the consumer: it re-dials and resubscribes with a bounded exponential backoff (100 ms up to 5 s). An ack failing on a closed connection is no longer retried forever. - Kafka: a failing offset commit is retried with an exponential backoff (100 ms up to 5 s) instead of every 100 ms.
Network timeouts
- STOMP: the broker connection, TLS and STOMP handshakes are bounded by
connectTimeout(default 30 s), so a blackholed broker no longer hangsStart,Stopand theCamelContextshutdown. - Mail: every SMTP path (plain, SMTPS,
requireStartTLS) dials withconnectionTimeoutand sets a deadline before each protocol phase; the retry backoff stops as soon as the exchange context ends. - Mail: SMTP retries are classified by reply code (
5xxpermanent,4xxtransient) instead of words in the error text.
Memory bounds
- File consumer: the map of ingested files is capped by
maxSeenEntries. - exec: stdout and stderr are capped by
maxOutputSize. - MongoDB:
findresults are capped bymaxResults.
Core and other components
- Choice: a
Whenexpression is parsed once, which removes a data race when a failed parse was retried on every exchange. - SFTP: a move no longer attempts the rename when creating the destination directory failed (a
file does not existerror was mistaken for an existing directory).
See the CHANGELOG for the full list.
New options
| Component | Option | Default | Description |
|---|---|---|---|
stomp | connectTimeout | 30s | Timeout of the TCP connect plus the TLS and STOMP handshakes |
file | maxSeenEntries | 100000 | Ingested files remembered to skip duplicate events (0 = unlimited) |
exec | maxOutputSize | 33554432 (32 MiB) | Bytes kept from stdout and from stderr (0 = unlimited); sets CamelExecOutputTruncated when exceeded |
mongodb | maxResults | 10000 | Documents a find returns (0 = unlimited); sets CamelMongoDbResultsTruncated when exceeded |
anthropic, ollama | allowHeaderOverride | false | Allow the override headers to replace the URI settings |
For the changed defaults of v0.14.0, read the v0.14.0 release notes.