docs: reflect 0.16.8-sqd.1 as npm latest (README matrix + dist-tag note fix) (#141)

dzhelezov · claude · web-flow · commit af80c2f6810b · 2026-07-10T17:46:00.000+02:00
* docs: reflect 0.16.8-sqd.1 as npm latest (README matrix + versions.json dist-tag note) 0.16.8-sqd.1 is now the npm 'latest' dist-tag. Update the README Ponder- versions matrix (add the 0.16.8 latest row; 0.16.7-sqd.1 is now published but has no dist-tag; seam range → 0.15.17-0.16.8) and correct the versions.json note, which #138 wrongly said 0.16.7-sqd.1 'keeps its ponder-0.16.7 dist-tag' — no such tag exists (npm view dist-tags shows only latest, ponder-0.16.6, ponder-0.15.17). 0.16.7-sqd.1 stays installable by exact version; a ponder-0.16.7 tag would have to be added deliberately. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(versions): correct 0.16.7 row — superseded as latest, no dist-tag The 0.16.7-sqd.1 note still read 'As the newest ponder version it publishes with --tag latest', now stale: 0.16.8-sqd.1 took over latest. Bring it in line with the 0.16.6/0.15.17 rows' dist-tag-status convention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
diff --git a/README.md b/README.md
@@ -95,11 +95,12 @@ Full adoption path — check, swap, run, validate, roll back — in [`MIGRATION.
 
 ## Ponder versions
 
-`@subsquid/ponder@X.Y.Z-sqd.<rev>` is `ponder@X.Y.Z` plus the Portal layer, pinned to a known Ponder version; `-sqd.<rev>` ships a fork-side fix on the same Ponder version. The seam is stable across 0.15.17–0.16.7.
+`@subsquid/ponder@X.Y.Z-sqd.<rev>` is `ponder@X.Y.Z` plus the Portal layer, pinned to a known Ponder version; `-sqd.<rev>` ships a fork-side fix on the same Ponder version. The seam is stable across 0.15.17–0.16.8.
 
 | Ponder | `@subsquid/ponder` | Status |
 |---|---|---|
-| 0.16.7 | `0.16.7-sqd.1` | **latest** |
+| 0.16.8 | `0.16.8-sqd.1` | **latest** |
+| 0.16.7 | `0.16.7-sqd.1` | published · pin exact (no dist-tag) |
 | 0.16.6 | `0.16.6-sqd.2` | published · dist-tag `ponder-0.16.6` |
 | 0.15.17 | `0.15.17-sqd.2` | published · dist-tag `ponder-0.15.17` |
 
diff --git a/versions.json b/versions.json
@@ -12,15 +12,15 @@
       "rev": 1,
       "status": "verified",
       "published": true,
-      "note": "0.16.8-sqd.1 is cut from the SAME Portal layer as 0.16.7-sqd.1 (invariant-first re-architecture INV-1…INV-18 + the correctness wave through the #47 mid-range-204 fix, the #50 bounded-time-to-first-commit warmup, the #20/#94 needed-field scoping, and the #110/#111 access_list honest-NULL fix), grafted onto ponder@0.16.8. The wiring patch is byte-identical to 0.16.6/0.16.7 (sha256 ddd12dd5…, same 10/10 files) — it applies cleanly (zero rejects), builds, and passes the full current Portal suite (312 tests — grown from the 302 at the 0.16.7 cut as the correctness wave added coverage) on ponder@0.16.8 (scripts/sync-upstream.sh 0.16.8 --test). 0.16.7→0.16.8 is a realtime-only upstream change: it adds isAsyncExecutionChain (chainId 143/10143) in sync-realtime/index.ts + utils/finality.ts so async-execution chains can surface blocks before logsBloom is execution-ready — neither file is on the graft surface (sync-historical, runtime/historical, sync-store, rpc, sync), so the seam is untouched and the 81 Portal realtime tests (portal-realtime-wire/portal-realtime/realtime-standardize) pass unchanged. No fresh RPC byte-diff on 0.16.8; compat rests on seam-identity + the full suite, as for 0.16.7/0.15.17. As the newest ponder version it publishes with --tag latest; it was published as 0.16.8-sqd.1 on 2026-07-10 and is now the default `npm install @subsquid/ponder`, superseding 0.16.7-sqd.1 as latest (which keeps its ponder-0.16.7 dist-tag)."
+      "note": "0.16.8-sqd.1 is cut from the SAME Portal layer as 0.16.7-sqd.1 (invariant-first re-architecture INV-1…INV-18 + the correctness wave through the #47 mid-range-204 fix, the #50 bounded-time-to-first-commit warmup, the #20/#94 needed-field scoping, and the #110/#111 access_list honest-NULL fix), grafted onto ponder@0.16.8. The wiring patch is byte-identical to 0.16.6/0.16.7 (sha256 ddd12dd5…, same 10/10 files) — it applies cleanly (zero rejects), builds, and passes the full current Portal suite (312 tests — grown from the 302 at the 0.16.7 cut as the correctness wave added coverage) on ponder@0.16.8 (scripts/sync-upstream.sh 0.16.8 --test). 0.16.7→0.16.8 is a realtime-only upstream change: it adds isAsyncExecutionChain (chainId 143/10143) in sync-realtime/index.ts + utils/finality.ts so async-execution chains can surface blocks before logsBloom is execution-ready — neither file is on the graft surface (sync-historical, runtime/historical, sync-store, rpc, sync), so the seam is untouched and the 81 Portal realtime tests (portal-realtime-wire/portal-realtime/realtime-standardize) pass unchanged. No fresh RPC byte-diff on 0.16.8; compat rests on seam-identity + the full suite, as for 0.16.7/0.15.17. As the newest ponder version it publishes with --tag latest; it was published as 0.16.8-sqd.1 on 2026-07-10 and is now the default `npm install @subsquid/ponder`, superseding 0.16.7-sqd.1 as latest. 0.16.7-sqd.1 remains published and installable by exact version; no dist-tag currently points at it (it was latest before 0.16.8-sqd.1, and npm does not auto-retag a superseded version — a ponder-0.16.7 tag would have to be added deliberately)."
     },
     {
       "ponder": "0.16.7",
       "wiring": "wiring/0.16.7.patch",
       "rev": 1,
       "status": "verified",
       "published": true,
-      "note": "0.16.7-sqd.1 is cut from the SAME Portal layer as 0.16.6-sqd.2 (invariant-first re-architecture INV-1…INV-18 + the correctness wave through the #47 mid-range-204 fix, the #50 bounded-time-to-first-commit warmup, and the #20/#94 needed-field scoping), grafted onto ponder@0.16.7. Seam identical to 0.16.6 — the 0.16.6 wiring patch applies cleanly (zero rejects, 10/10 files), builds, and passes the full Portal suite (302 tests) on ponder@0.16.7 (CI matrix). 0.16.6→0.16.7 is one DB-layer PR (ponder-sh/ponder#2314: live-query notification batching, drops the 100-table limit) touching database/actions, drizzle/onchain, build/schema, bin/createViews — none of the graft surfaces (sync-historical, runtime/historical, sync-store, rpc, sync). No fresh RPC byte-diff on 0.16.7; compat rests on seam-identity + the full suite, as for 0.15.17. As the newest ponder version it publishes with --tag latest."
+      "note": "0.16.7-sqd.1 is cut from the SAME Portal layer as 0.16.6-sqd.2 (invariant-first re-architecture INV-1…INV-18 + the correctness wave through the #47 mid-range-204 fix, the #50 bounded-time-to-first-commit warmup, and the #20/#94 needed-field scoping), grafted onto ponder@0.16.7. Seam identical to 0.16.6 — the 0.16.6 wiring patch applies cleanly (zero rejects, 10/10 files), builds, and passes the full Portal suite (302 tests) on ponder@0.16.7 (CI matrix). 0.16.6→0.16.7 is one DB-layer PR (ponder-sh/ponder#2314: live-query notification batching, drops the 100-table limit) touching database/actions, drizzle/onchain, build/schema, bin/createViews — none of the graft surfaces (sync-historical, runtime/historical, sync-store, rpc, sync). No fresh RPC byte-diff on 0.16.7; compat rests on seam-identity + the full suite, as for 0.15.17. Published as 0.16.7-sqd.1 with --tag latest; superseded as latest by 0.16.8-sqd.1 on 2026-07-10 and now has no dist-tag (installable by exact version — a ponder-0.16.7 tag would have to be added deliberately)."
     },
     {
       "ponder": "0.16.6",
