v0.20.0
Version v0.20.0, dated November 16, 2026, follows a code review of the core routing engine and the file component. Several HTTP routes can now share one port, nine findings are fixed, and a few visible behaviours change. Every component and observability module at v0.20.0 requires core v0.20.0.
Behaviour changes
- HTTP routes share a port: consumers of one
HTTPComponentwhose URIs share ahost:portnow share a single listener and are told apart by their path, soFrom("http://0.0.0.0:8080/orders")andFrom("http://0.0.0.0:8080/health")can live in the same context. The port is released when the last of them stops, and a path already served on the port is rejected atStart. The consumer middleware now wraps each consumer’s handler: a path no consumer serves answers 404 without going through it. - Route start order:
CamelContext.Startstarts the routes consuming fromdirect:first, then the others, each group in declaration order. A consumer that routes an exchange as soon as it starts finds thedirect:routes it calls already running. file— relativemove/moveFailed: a relative directory is resolved next to the consumed file (move=.donesends/data/in/a.txtto/data/in/.done/a.txt) instead of against the working directory of the process. Files lying in those directories are never consumed again, including withrecursive=true.file— backlog at startup: files already present in the directory are consumed by the consumer goroutine instead of fromStart(), so a backlog no longer blocks the route and the context from starting.ParseURIerrors: the error no longer quotes the raw URI nor the offending fragment; it reports the redacted URI and the kind of failure (invalid URI "ftp://user:xxxxx@host/dir": invalid percent-encoding).
Fixes
- HTTP
Content-Type: aContent-Typethe route sets to the value the request carried was dropped as an echoed inbound header, so a JSON API answering a JSON request repliedtext/plain.Content-Typeis now exempt from the echo filter; a route that does not set it returns the request’s. LoopandStop(): the Stop EIP inside a loop was swallowed and the steps after the loop still ran.Stop()now ends routing of the exchange; any other stop signal (Filter,Sample…) still only ends the loop.Resequencercontext: buffered exchanges kept the context of the request that brought them and were delivered downstream with a cancelled context once that request was over. They are now delivered under the route’s lifecycle context.Resequencererrors: the downstream failure of a buffered exchange was returned to whichever exchange triggered the delivery, failing (and redelivering) the wrong message. Only an exchange’s own failure is returned to it; the others are logged.- Idempotent Consumer: the key of a failed exchange was rolled back with the exchange context, often already cancelled, so a context-aware repository (Redis) kept the key and the redelivered message was dropped as a duplicate. The rollback now ignores the cancellation and is bounded to 30s.
- Credential redaction:
RedactURIreturned a URI it could not parse unchanged, credentials included (a password holding a stray%). Such URIs are now masked textually.
Upgrading
- A
fileroute relying on a relativemove/moveFailedresolved against the process working directory must switch to an absolute path. - Code matching the text of a
ParseURIerror must be updated. - An HTTP route that changes the body without setting
Content-Typenow returns the request’sContent-Typeinstead of a sniffed one: set it explicitly.
See the CHANGELOG for the full list of changes.