Repository navigation
chore(release): 1.7.0 — a write path that survives its transport - #40
Merged
Merged
Conversation
The three packages move to 1.7.0 together, and the release note records what shipped, what was verified, and what was not. Contents: `jam jira write-plan` / `jam jira write-apply`, plans persisted to ~/.jam/write-plans/ so both transports read one store, and integrity by re-derivation rather than a signature (JAM_WRITE_PLAN_TAMPERED). No new behaviour is added here - this commit is version, lockfile and note. Gate: npm run release:verify - build, test, release:check, smoke, all green. Not exercised, and said so in the note: JAM_WRITE_UNCERTAIN, whose trigger is an ambiguous transport failure that cannot be produced against real Jira on demand. Also recorded there: `--input` JSON does not survive PowerShell quoting, which matters because the sessions that lose their MCP tools are often on Windows. Co-Authored-By: Claude Opus 5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Version, lockfile and release note for 1.7.0. No behaviour is added here — the change itself merged as #39.
The three packages move to 1.7.0 in lockstep and depend on each other at that exact version.
Contents of the release
jam jira write-plan/jam jira write-apply— the same application write path the MCP tools use, addressed to the shell~/.jam/write-plans/, shared by both transports, so a plan made through MCP can be applied from the shell after the tools stop answeringJAM_WRITE_PLAN_TAMPEREDdocs/decisions/adr-jira-write-plane.md§"Where plans live" rewritten, including what was lostGate
Recorded as not verified
JAM_WRITE_UNCERTAINwas not exercised. Its trigger is an ambiguous transport failure that cannot be produced against real Jira on demand; only its code path was read. In the note under Known limitations.--inputJSON does not survive PowerShell quoting. Not specific to JAM, but it matters here because the sessions that lose their MCP tools are often on Windows. Also in the note, with the follow-up options.Published acceptance runs after
release.yml, before the tag — perdocs/operations/release.md, a tag is created only after acceptance passes against the published packages.🤖 Generated with Claude Code