Camel versions

Each integration runs on one Camel line, and different integrations can run on different lines in the same installation. Weik.io 2026.2 has two lines, 4.18.5 and 4.22.1, both on OpenJDK 21. The backend carries a Camel launcher for each line, so the hub builds every version on the line it asks for. The agent image carries the Java runtime that runs it.

List the lines#

$ weikio get camel-lines

The list has each line with the version of Camel’s kamelet catalog pinned to it, the digest of the launcher that builds it and the lowest Java version it needs. It also marks the installation’s default line, which an integration runs on when it asks for no line.

Pick a line#

Name the line in integration.yaml:

name: erp-invoice-export
version: 1.0.0
camelVersion: "4.22.1"

A range such as 4.22.x picks the newest line of that minor version the installation lists. You can also set camel.jbang.camel-version in the folder’s application.properties, the setting Camel JBang uses. When both are there, application.properties decides, because Camel JBang obeys it too.

The version records the exact Camel version it was built with, and weikio describe version prints it with the kamelets version and every jar. weikio dev run runs the folder on the same line on your machine.

Move an integration to another line#

A Camel upgrade is a new version. weikio version create builds the next version from the integration’s current files on another line:

$ weikio version create finance/erp-invoice-export --camel-version 4.22.1 --note "Camel 4.22"

Deploy the new version to devtest, and promote it once it runs as it should. Production keeps running the version on the older line until then, because the two lines run side by side.

What differs between the lines#

• The build validates routes with Camel’s own check on 4.22.1, so on that line a route Camel refuses fails during the apply. On 4.18.5 the same route fails when it starts.
• Each line has its own kamelet catalog version, so a catalog kamelet can differ between the lines.
• Change tracking uses the Debezium version each line’s Camel component brings: 3.6.1.Final on 4.22.1 and 3.4.1.Final on 4.18.5.
• On 4.22 a trace leaves out the single steps inside a route, which keeps the traces of a busy route small.

New Camel lines arrive with Weik.io releases. The roadmap says what the coming releases bring.