Shipping Changes
After the first publish in chapter 4, every change — a fix from testing, a review finding, a new field, a new component — goes out the same way: you publish again. There is no update command.
What this chapter covers is what publishing again actually does — to what the instance serves, and to the flows already running on it — and why the command that looks like the way to force it is the most dangerous one in the CLI.
The prompt
Don't remove anything on the instance. Bump the version in component.json of every component you changed since the last publish, then publish.
It reads like over-instruction, and it is not. The test-connector skill tells the agent that the way to deal with a component that looks stale on the instance is to remove it and publish it again, with the commands written out. Left alone, an agent that sees something it did not expect follows that instruction — no stop, no question. Given this prompt, it compares the instance's packages with your files, bumps only what changed, and publishes.
What publishing again does
The instance serves the version you published last, whatever component.json called it. Publishing stores a new copy and retires the ones before it: they stay in storage, but nothing is served from them any more.
a changed component, version bumped
the new version only
Running flows move to it by themselves — see below
a changed component, same version
the new code, within seconds
It works, but nothing records that anything changed
an unchanged component
the same thing as before
Harmless
Bump component.json's version whenever that component changes anyway, and the bundle's with a changelog line. Not because a same-version republish is unpredictable — it is not — but because the version is the only record of what is running, the only thing a changelog can point at, and the difference between a change that flows pick up on their own and one that stops them (Flows follow the version).
Shared files — lib.js, auth.js, quota.js — sit beside the components, so editing one changes components whose own files did not move. Treat it as a change to every component that uses it.
Bump the bundle, and say what changed
Nothing bumps bundle.json for you:
{
"name": "acme.eventbrite",
"version": "1.1.0",
"changelog": {
"1.1.0": [
"Create Event: Currency is now a dropdown of the 25 currencies Eventbrite accepts."
]
}
}A change that breaks existing accounts or flows is a major version, and the changelog should say so. The usual one is an auth change — Day-to-Day Work.
Seeing what the instance actually serves
Without -m the listing is component names only, and the version — the thing you are checking — is not in it.
appmixer component get is a different question. It hands you every copy ever published of that component, newest and retired alike, all under the same path inside the zip:
Repeated paths there are history, not a broken instance. unzip extracts only the last of them, so a quick look tells you nothing either way. Read the versions out of the archive without extracting it if you want to see what has been published over time.
Flows follow the version
A flow names the version of each component it uses — E2E flow files in artifacts/test-flows/ carry a version next to each type — but that name is a floor, not a pin. At every execution the engine takes the newest published version compatible with it, which means the same major:
You publish
A running flow that names 1.0.0
1.0.1, 1.1.0
switches to it within seconds, by itself. No re-import, no restart
1.1.0 again, with different code
runs the new code, just as quietly
2.0.0
stops processing at that component
The first two are what makes shipping a fix cheap: publish, and the flows that use it are already on it. The flow file still says 1.0.0; what ran is in the logs, as componentVersion.
After an ordinary bump, re-running the E2E flows needs nothing special:
After a major, update the version in the flow files first, then import and run:
Never remove to update
A version bump ships a change; remove never needs to. Its legitimate use is clearing components you renamed, so the old names stop being offered. For components you deleted from the connector, use appmixer publish --replace-all.
Do not count on your agent to stop first. Nothing in the skills requires a stop before appmixer remove; some agents ask on their own, some do not. Draw the line yourself:
In the prompt — "Before any command that removes or overwrites something on the instance, stop and ask me."
In the agent's permissions — set the agent to always ask before
appmixer remove. How, per agent, is indocs/agents.mdin the appmixer-skills repository.
After any remove, confirm it happened before publishing again — a 502 or 504 may or may not have done anything:
Verify
The component you changed is at its new version, and the ones you did not touch are where they were. appmixer bundle ls cannot answer this — it lists installed bundles, and publishing does not register one. Then re-run the E2E flows: a patch or minor bump reaches them by itself, a major one needs their pins updated first.
Next: Day-to-Day Work.
Last updated
Was this helpful?
