Skip to content

JAM v1.4.4

Choose a tag to compare

@github-actions github-actions released this 01 Sep 07:30
· 13 commits to main since this release
6125662

JAM 1.4.4 makes project setup deterministic when a machine carries old
settings, and stops "mixed" credentials from reading as a fault. Two field
reports drove it: an operator had to hand-edit ~/.jam/projects.yaml before
--project would take effect, and a working credential split across the OS
store and one exported token was investigated as if it were broken.

What changed

  • --project <KEY> decides the run. It already beat a personal binding,
    JAM_PROJECT_KEY and a legacy preset entry; that is now pinned by tests,
    and a stale binding is repaired through the ordinary replace plan. Nothing
    has to be deleted by hand first.

  • The repository's committed key is never overwritten silently. It used
    to win over --project while being reported as explicit, so the flag
    looked honoured when a different key was in use. A disagreement now stops:

    {
      "status": "user_action_required",
      "code": "JAM_PROJECT_KEY_CONFLICT",
      "requested": { "key": "PROJECT", "source": "explicit" },
      "existing":  { "key": "OTHER",   "source": "repository" }
    }

    No change is applied over a conflict, in any entry point. Which Jira
    project a repository belongs to is the team's decision.

  • Key provenance is reported. Sources are explicit, repository,
    env, binding or preset, and a plan carries project.keySource.

  • Credential sources, per field. describe() and auth status --json
    carry a sources map naming which source supplied JIRA_BASE_URL,
    JIRA_EMAIL and JIRA_API_TOKEN. Names only — no value is ever printed.

  • doctor --json gains a per-axis diagnosis: credentials,
    projectBinding, runtime, registration, liveToolset,
    jiraAuthentication, jiraProjectAccess. A failure is attributed instead
    of guessed at, and mixed is a WARNING on the credentials axis — never a
    failure on its own. Whether Jira accepts the credentials stays on its own
    axis.

Install / Upgrade

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

Optional persistent command:

npm install -g @jam-mcp/launcher@1.4.4

Existing users: re-run setup. Bindings, runtime selection, host registration
and credentials are untouched — a stale binding is repaired in place.

Agent setup

The canonical entry is unchanged; --project is what became reliable:

npx --yes @jam-mcp/bootstrap@1.4.4 setup --agent --project PROJECT

Compatibility

  • Node 20 or newer, unchanged. The five-tool MCP surface is unchanged.
  • Additive JSON: project.keySource, requested/existing on a conflict,
    sources on credential descriptions, diagnosis on doctor.
  • One new stop: JAM_PROJECT_KEY_CONFLICT. It fires only where a run
    previously used a different key than the flag asked for.

Verified

  • server 475 + launcher 39 tests, typecheck, build, release:check, pack and
    tarball smoke — green locally on Windows and on CI (Ubuntu/Windows ×
    Node 20/22).
  • Live matrix against the published artefact: stale binding replaced
    OLDKEY → the requested key; a disagreeing repository key stopped with
    JAM_PROJECT_KEY_CONFLICT and zero changes; an agreeing repository key
    reported keySource: repository.
  • Real project acceptance: setup --agent --project <KEY> reached ready
    with all seven diagnosis axes OK, including a live Jira read, and no
    credential value in any output.
  • A mixed credential (store plus one exported token) reported WARNING with
    its per-field sources while the overall status stayed ready.

Known limitations

  • A repository conflict is deliberately not auto-resolvable: JAM reports both
    sides and stops, and someone has to decide with the team.