Tags give the ability to mark specific points in history as being important
-
v0.0.6
c8350eae · ·codemap 0.0.6 — checks that had never been shown the thing they must reject Evidence rather than behaviour: one new item (a warm server that says when it is running code the installed distribution has moved past) and three that change what is known about the tool rather than what it does — every contract rule mutation-tested on a real tree, the target guard's decision tested directly, and a defect measured on a flat layout where it merged two trees rather than replacing one. Schema 0.13, unchanged; no rebuild needed. Published as codmap 0.0.6. Superseded within the day by 0.0.7: the new diagnostic could not fire as shipped.
-
v0.0.7
364fd765 · ·codemap 0.0.7 — the one thing 0.0.6 added, now actually reachable R1-C38-f1: `tool_restart_needed` compared a cached version with itself, so a warm server never warned that it was running superseded code. The installed side is now read fresh per call, and the regression test changes only the installation. Schema 0.13, unchanged. Verified on the published wheel by driving the scenario the feature exists for: serve, change the installation underneath, ask — reported on both `stats` and `reload`. Published as codmap 0.0.7.
-
v0.0.5
9523dc1d · ·codemap 0.0.5 — three answers that were well-formed and wrong Correctness release, no schema change (graphs stay 0.13; rebuild anyway, two fixes change what a graph says). - R1-C33 the declared signature travels with the `query` dossier - R1-C34 the stored signature dropped parameter kind (14.3% of codemap's own functions, 16.3% of bquant's), which had silently disabled three apidiff rules - R1-C35 a gate that found no contract did not say where it looked, nor that this exits 0 - R1-C36 a build could analyse a different package with the same name, with exit 0 and a complete graph of the wrong code Verified from PyPI in a clean venv outside any checkout, from a working directory holding a package of the same name as the target: the build described the directory it was given, the graph carries no absolute paths, the signature renders `*args` and the keyword-only marker, the class dossier carries its constructor, and `check` names the file it searched. 713 tests, 2 skipped. -
v0.0.4
45de657c · ·codemap 0.0.4 — schema 0.13 Nine Fixed entries since 0.0.3, and all but one came from a second real user's tree: R1-C28 (limit envelope), R1-C29 (lazy imports are dependencies, and a cycle has two kinds), R1-C30 + f1 + f2 (calls through a function-local import, through a re-export, and a gate that judged a subset in silence), R1-C31 (one path origin per graph), R1-C32 (report --format json), M3.2 + f1 (the watch loop, with an adaptive debounce). Schema 0.12 -> 0.13: a repo-scoped graph now has one origin for its paths. Rebuild those; a single-package graph is byte-identical. Published as codmap 0.0.4; verified from PyPI in a clean venv outside any checkout: schema 0.13, provenance.tool {"name": "codemap", "version": "0.0.4"} with no commit, which is the correct no-checkout answer. -
v0.0.3
4c2f8c6f · ·codmap 0.0.3 — the first published release First release on PyPI, as the distribution `codmap` (the command, the import and the repository stay `codemap`; the bare name was taken). Ships everything that had accumulated since 0.0.2: flat-layout support, source-visible references, the deep tier as a union with the fast one, graph provenance (schema 0.12), test mapping, hard-Python robustness, and M20 — CI, honest package metadata, and a measured Python range. Verified from PyPI into a clean venv, run outside any source tree.
-
v0.0.2
68a0908e · ·codemap v0.0.2 — first internal cut (schema 0.11, 363 tests; attribute-access edges + incremental rebuild). Not published to PyPI.