Skip to content

JAM v1.4.3

Choose a tag to compare

@github-actions github-actions released this 31 Aug 03:22
· 19 commits to main since this release
5b8ad9e

JAM 1.4.3 makes the fresh Windows install actually work end to end. Every
defect found in a Windows field verification on a real project (2026-08-31) is fixed:
a fresh machine now always receives an MCP registration that runs, apply's
status stops contradicting itself, and Node 24 deprecation noise is gone from
every JSON surface.

What changed

  • npx PATH contamination (release blocker) — under
    npx --yes @jam-mcp/bootstrap@<version>, npx prepends its cache's
    node_modules/.bin to PATH, which contains a jam shim that vanishes when
    npx exits. The "does this machine have a persistent jam" measurement ran
    through that PATH, answered yes on every fresh machine, and setup then
    registered a bare jam serve that died immediately. The measurement now
    strips package-runner entries (_npx, node_modules/.bin) first: fresh
    machines get the always-runnable npx pin, and bare registration happens only
    over a real persistent install.
  • Apply status honesty — setup apply used to answer
    already_configured alongside changesApplied: true. Executed changes now
    answer applied.
  • DEP0190 removal — every spawnSync(cmd, args, {shell: true}) site
    (host probes, live toolset, npm probe, launcher dispatch, dev scripts) now
    validates bare tokens and joins the argv itself; cmd.exe metacharacters are
    refused instead of concatenated. --json outputs are clean of warnings.

Install / Upgrade

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

Existing users: re-run setup; a stale or dead registration is replaced in
place. Bindings, runtime selection and credentials are untouched — verified
in-place against a live operating setup.

Agent setup

No change to the canonical entry:

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

Compatibility

  • Node 20 or newer, unchanged. The five-tool MCP surface is unchanged.
  • setup apply may now answer applied where it previously (wrongly) said
    already_configured after executing changes.

Verified

  • server 455 + launcher 39 tests, release:check, pack and tarball smoke —
    green locally on Windows and on CI (Ubuntu/Windows × Node 20/22).
  • Live Windows reproduction of the npx-PATH defect: with a contaminated PATH
    and no global jam, setup plan now proposes the npx pin (previously bare
    jam serve).
  • Published-registry fresh setup on Windows with zero manual installs:
    registered npx --yes @jam-mcp/launcher@1.4.3 serve boots, doctor --json
    reports ready on all three axes with 0 bytes on stderr, and the three read
    tools answer live Jira with meta.complete: true.
  • Non-mutating jira_write_plan exercised against live Jira (planId issued,
    nothing applied); structured error path confirmed.
  • In-place re-apply over an existing operating setup: already_configured,
    binding/registration/runtime preserved.

Known limitations

  • The GitHub Release for this version was created by the tag-triggered
    workflow of its day; the successor pipeline separates publish from
    finalization so acceptance always precedes the tag.