Skip to content

JAM v1.4.1

Choose a tag to compare

@colosair colosair released this 30 Aug 09:33
· 24 commits to main since this release
d6e6192

JAM 1.4.1 makes jam doctor answer the question that actually matters on a
half-upgraded machine: not just "is this package current", but "what does the
host registration launch, and what does that process really serve".

What changed

  • Doctor's three axes — package (the runtime this machine would run),
    registration (what the host CLIs have registered for this user, stale pins
    detected by version), and live (the registered command is actually
    launched and its tool list compared). A stale pin serving an older tool set
    no longer reads as ready.
  • Release smoke hardening: EPIPE fix in the published smoke, and the smoke now
    verifies the real consumer path.

Install / Upgrade

npx --yes @jam-mcp/bootstrap@1.4.1 init

Existing users: re-running setup repairs a stale registration; bindings and
credentials are untouched.

Agent setup

No change to the canonical entry:

npx --yes @jam-mcp/bootstrap@1.4.1 setup --agent

Compatibility

  • Node 20 or newer, unchanged. The five-tool MCP surface is unchanged.
  • doctor --json output gains the axes block (additive).

Verified

  • release:verify green on Ubuntu and Windows against Node 20 and 22 (CI).
  • Published via the Trusted Publishing workflow; registry verification and the
    published smoke ran inside it.

Known limitations

  • This body was restored after the fact (2026-08-31) from the recorded
    procedure and commit history; it claims no verification beyond those records.