Repository navigation
JAM v1.5.0
JAM 1.5.0 adds jam update: it moves this machine's registration to the
published release without re-running setup.
What changed
jam update. What goes stale in JAM is a line, not a directory — the host
launches JAM from a registration carrying an exact pin, and a newer JAM on the
registry changes nothing until that pin moves. Right after 1.4.6 was published
this machine measuredregistration: HOST_REGISTRATION_STALE (registered 1.4.5), and the command that fixed it wasjam setup --agent, which also
re-plans the project binding, credentials and everything else.jam update
does not call it. It proves the new build answers, re-registers the entry at
that version, reads the registration back, and runsdoctor— which is
config, credentials and one live read.- The order never removes first. The published build is verified before the
registration is pointed at it, so a failed update leaves the machine running
what it was running. - A host with no
jamentry is left alone. Registering JAM somewhere it was
never registered is adoption, andjam setupis where a person says they want
that. - The registry not answering is
UNKNOWN, never "up to date". - A registration that lands but is not healthy is rolled back to the pin that
was there. jam update check --jsonandjam update plan --jsonchange nothing.
Install / Upgrade
jam updateFrom nothing:
npx --yes @jam-mcp/bootstrap@1.5.0 initOptional persistent command:
npm install -g @jam-mcp/launcher@1.5.0Bindings, runtime selection, credentials and ~/.jam/projects.yaml are untouched
by an update.
Agent setup
The canonical entry is unchanged:
npx --yes @jam-mcp/bootstrap@1.5.0 setup --agentUpdating an already-configured machine is jam update, not setup --agent.
JAM updates JAM only — ASC has asc update, and neither calls the other.
Compatibility
- Node 20 or newer, unchanged. The five-tool MCP surface is unchanged.
- Additive CLI only: a new
updatecommand. Nothing existing changed shape. hostRegistrationaccepts a version, so a registration can name a release
other than the running build's — the rest of the argv is the line setup writes.
Verified
- Build, launcher + server tests,
release:check, pack and tarball smoke. - Ten new tests hold the order: check runs nothing, a pin that does not answer is
never registered, remove precedes add, the read-back is what reports success, a
failingdoctorrolls back, and setup is never invoked. - Real machine: 1.4.6 → 1.5.0 through the published artefact, with the project
binding, credentials and runtime mode compared before and after.
Known limitations
- Downgrade and pinning a specific version are not implemented.
- A bare global entry updates the global install and keeps the entry; rolling
that back is a re-install, and the command says so rather than pretending. - Live
issue.createremains unexercised, as in 1.4.6.