Repository navigation
Registries pin codegraph schema 9, every live index is schema 15: select BLOCKS on all three repos #124
Description
Measured 2026-10-16:
| repo | index schema | index extraction | registry pin (schema / extraction) |
|---|---|---|---|
| testgraph | 15 | 28 | 9 / 26 (journeys/testgraph.json:6-7) |
| honeyslate | 15 | 28 | 9 / 26 (journeys/honeyslate.json:132-133) |
| signedintake | 15 | 28 | 9 / 26 (journeys/signedintake.json:6-7) |
python3 -m testgraph.select --repo . --base origin/main --head HEAD on testgraph prints:
STATUS: BLOCKED — index not trustworthy
x codegraph schema 15 != pinned 9 — column semantics may have changed; ...
The pre-push hook always exits 0. So with the pin out of date, every push in these repos gets no answer, and the terminal gives no sign anything is wrong.
What has to happen first: re-check testgraph's queries against schema 15. The pin is there so that a renamed column fails loudly instead of quietly returning wrong rows. Bumping it without that check would remove the protection it exists for.
Then:
- bump
codegraph_schema_versionto 15 in all three registries - bump
codegraph_extraction_versionfrom 26 to 28. The index already warns that this pin is behind. - add a test or check that fails when a registry pin lags the deployed codegraph. That way a drift like this one shows up as a failure rather than going unnoticed.
Related: #79 (the previous bump, 8 → 9, made after verifying the queries).
Activity
chore: schema pin 9 -> 15, extraction pin 26 -> 28, after verifying t…
inth3shadows commentedon Oct 30, 2026
Fixed by #125 (6f48270: schema pin 9 → 15, extraction 26 → 28, after verifying the queries); the pin has since moved to 16 in #135 (81a3eb3).