Skip to content

v1.6.0

Choose a tag to compare

View all tags
@kgilpin kgilpin released this 21 Sep 21:07
· 13 commits to main since this release
v1.6.0
7070a30
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's changed

appmap-review: compare two recordings made by hand

The compare no longer needs gold traces. Give it two recordings, for example one Postman run recorded on each of two branches:

node "${CLAUDE_SKILL_DIR}/assets/review.mjs" compare --base-appmap <file> --head-appmap <file>
  • Both files are copied to one trace name, so files named by timestamp compare as one trace instead of one removed plus one new. --name sets that name. The default is the basename the two files share, or recording.
  • This mode reads no manifest and no gold_traces/. --base and --head are optional and only name the source diff. --appmap-cli picks the CLI, since there is no manifest to name it.
  • The skill has a short section on what differs in this mode: values are real instead of sanitized tokens, coverage is only what the run touched, and the report says the two sides are hand-made recordings of one scenario.

appmap-review: moved blocks are named, and each diff is also text

With AppMap CLI 3.204.0 or later, a block of calls that moved to another caller is reported as one move. Older CLIs showed it as a removal plus an addition.

For every changed trace the summary now prints:

  • how many nodes changed, by kind: added, removed, changed, moved
  • one line per moved block, naming the caller it left and the caller it is under now, or "reordered within" when the caller is the same
  • the labels on the changed nodes
  • the path to the same diff as text, one line per changed node, under out/report/text/. This reads better than JSON for large recordings.

An older CLI still runs. The summary then says that a moved block shows as removed plus added. A block that moved and also changed inside still shows as removed plus added, because the CLI pairs a move only when the block is identical. The skill explains how to read that.

Step 5 of the review recipe gains the questions to ask about a moved block: which caller the diff touched, what now runs before and after the block, and whether anything involved carries a label.

appmap-review: the report records how the review was run

The helper's summary ends with the command line as typed and the directory it ran in. The report header gains a one-line Method summary, and a closing section holds the request, the compare command, the working directory, and the evidence path. A reader can rerun the compare from that. For two hand-made recordings, that command is the only record of which files were compared.

appmap-setup: install the CLI without an IDE

The skill now has steps to install the AppMap CLI by hand when no IDE is available: fetch the release manifest, pick the asset for this machine's OS and CPU, check its sha256, and put it on PATH as appmap.

Upgrading

Nothing to change in projects. Manifests and committed baselines stay valid. Moved-block reporting needs AppMap CLI 3.204.0 or later.

Full changelog: v1.5.0...v1.6.0

Assets 2
Loading