Versions and the developer loop
Weik.io 2026.2weikio apply publishes an integration as an immutable version that Weik.io builds once. Before you publish, weikio dev run runs the folder on your machine. Product page · Video
Watch: Change it and run it again, 4:02
The video publishes an edited route as a new version with weikio run and lists the versions the installation keeps.
This part of the video couldn't be loaded.
On this page
Publishing and deploying are separate steps. You publish a version with weikio apply and run it in an environment with weikio deploy. While you develop, weikio run does both in one step.
Publish a version#
$ weikio apply -f ./finance/Target: https://hub.example, project finance (from finance/project.yaml), environment devtest (context)
project finance unchanged
variable finance/erp-url unchanged
variable production/finance/erp-url updated
integration finance/erp-invoice-export created (version 1.0.0, built in 20.8 s)
Nothing new is running yet. To run it:
weikio deploy finance/erp-invoice-export --env devtestA version can’t change once it’s published, like a package published with npm publish. Applying the same files again prints unchanged. An apply that changes the files without raising the version fails:
$ weikio apply -f ./finance/erp-invoice-exportTarget: https://hub.example, project finance (from finance/project.yaml)
integration finance/erp-invoice-export refused: Version '1.0.0' is already published.
Set another with --version <version>, or bump it with --bump patch.--bump raises the version in integration.yaml the way npm version does, and publishes it:
$ weikio apply -f ./finance/erp-invoice-export --bump minorTarget: https://hub.example, project finance (from finance/project.yaml), environment devtest (context)
integration.yaml updated to 1.1.0
Uploading 2/9 files, building...
integration finance/erp-invoice-export updated (version 1.1.0, built in 17.3 s)
Nothing new is running yet. To run it:
weikio deploy -f ./finance/erp-invoice-export --env devtestAn integration whose integration.yaml has no version: line starts at 0.1.0 and gets the next patch version on each apply that changes it. weikio init writes no version line, so your first integrations are numbered this way until you add one.
What the build does#
The CLI sends only the files Weik.io doesn’t have yet, by their content hash, so a later version uploads only what changed. Weik.io then builds the version once:
- On Camel 4.22.1 it validates the YAML routes with Camel, so an invalid route fails the apply with Camel’s message.
- It resolves the jars of the integration’s Camel line and of every component and dependency the integration uses.
- It compiles the Java beans with
javac. - It adds the jars every integration needs for logging and OpenTelemetry.
- It stores every file and jar in the project’s store by its SHA-256 hash and writes a manifest of the set.
Resolving Camel’s libraries is most of a first build, which takes about 15 seconds. A build that changes only configuration is done in a second or two. The agents fetch only the files they don’t have yet, so moving from 1.1.0 to 1.2.0 with one changed route fetches that one file.
Each step of a build has 15 minutes. When a step runs longer, the build fails with an error that mentions the step.
Each hub server runs one build at a time for every two CPU cores, or one build if it has a single core. The builder section of doctor shows the number. An apply that finds no free build slot within two minutes writes nothing and fails with 503 too_many_builds and Retry-After: 30. Apply the same files again after 30 seconds.
A hub server whose kernel can’t limit a build step’s network connections builds nothing until a platform administrator allows builds, as Builds are stopped describes.
What a version contains#
$ weikio get versions finance/erp-invoice-exportVERSION CAMEL CREATED BY NOTE DEPLOYED IN
1.1.0 (latest) 4.22.1 2026-09-16 14:31 UTC anna@example.com invoice mapper v2 -
1.0.0 4.22.1 2026-09-15 09:12 UTC anna@example.com - devtest, productionweikio describe version finance/erp-invoice-export 1.1.0 prints one version in full:
- The source and bundle digests
- The exact Camel version and the kamelets version
- The dependencies, and the kamelets with their source
- Every jar with its digest
- The names of the variables and secrets the routes use
applied from <repository>@<commit>when a pipeline published it
Weik.io keeps the build log with the version.
weikio version compare finance/erp-invoice-export 1.0.0 1.1.0 prints every file that differs between two versions as a unified diff. The Versions section of the integration’s page in the admin UI shows the same.




Run it on your machine first#
Before you publish, weikio dev run runs the folder on your machine with Camel JBang. It runs on the integration’s Camel line with the environment’s values and with the project’s and the platform kamelets:
$ weikio dev run ./erp-invoice-export --env devtestThe CLI finds the variable names in the folder itself, so the integration doesn’t have to be applied first. The kamelets that publish and receive events get local stand-ins.
Secret values stay out of the run unless you add --with-secrets, which reveals them and records each reveal in the audit log. Add --reload to turn on Camel’s reloading, so a route you save reloads in the running process.
Check before you apply#
weikio validate checks the folder before anything is built:
- The fields of each document
- Each document’s name
- The fields of
integration.yamland its dependencies - The placeholders
- The YAML of the route files
For most kinds, a name can use hyphens but otherwise only lower-case letters and digits. A variable or secret name can also use capitals and the characters . and _. A kamelet name can also use capitals and _. An API version can have a name such as 1.0.0 or v2.
Run weikio validate in a pipeline to fail early.
$ weikio validate -f ./finance
$ weikio diff -f ./finance --env devtest
$ weikio apply -f ./finance --env devtest --dry-runweikio diff and weikio apply --dry-run show what an apply would do:
- Which versions it would create
- Which variables would change
- Which deployments would move
- What would fail
An unknown route step passes validate and diff. On Camel 4.22.1 the apply’s build finds it, so a pipeline catches it in its devtest job.