chore(compat): register ponder@0.16.9 as a tested compat version (published:false)#148
Merged
Conversation
…false) Upstream `ponder` published 0.16.9 as `latest` on 2026-07-10, so a fresh `npm install ponder` now resolves to a version the fork didn't yet cover. This adds the compat row + wiring/0.16.9.patch (a verbatim copy of wiring/0.16.8.patch). Verification (`scripts/sync-upstream.sh 0.16.9 --test`): - 0.16.8→0.16.9 is a single-file upstream change: src/indexing-store/cache.ts only (ponder-sh/ponder#2323 — fix p.bytes() bytea encoding on the Postgres COPY flush path, emitting \x<hex> for Buffer values to fix "DelayedInsertError: invalid byte sequence for encoding UTF8: 0x00"). Confirmed by diffing the 0.16.8 and 0.16.9 npm tarballs. - indexing-store/cache.ts is off the graft surface (sync-historical, runtime/historical, sync-store, rpc, sync, sync-realtime); every upstream file the wiring patch modifies is byte-identical between 0.16.8 and 0.16.9, so the patch applies cleanly (zero rejects). - builds, and the full Portal suite is 328/328 green on ponder@0.16.9. - The fork passively inherits the upstream bytea-COPY correctness fix. published:false — publishing to npm is a deliberate, human-reserved step; 0.16.8-sqd.1 stays --tag latest until then. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Upstream
ponderpublished 0.16.9 aslateston 2026-07-10, so a freshnpm install pondernow resolves to a version the fork didn't yet cover. This registers the compat row and addswiring/0.16.9.patch(a verbatim copy ofwiring/0.16.8.patch).What changed upstream (0.16.8 → 0.16.9)
A single source file:
src/indexing-store/cache.ts— ponder-sh/ponder#2323: fixp.bytes()bytea encoding on the PostgresCOPYflush path (emit\x<hex>forBuffervalues), fixingDelayedInsertError: invalid byte sequence for encoding "UTF8": 0x00. Confirmed by diffing the 0.16.8 vs 0.16.9 npm tarballs (onlycache.ts+ its compileddist+CHANGELOGdiffer).Why the seam is untouched
indexing-store/cache.tsis not on the graft surface (sync-historical,runtime/historical,sync-store,rpc,sync,sync-realtime). Every upstream file the wiring patch modifies is byte-identical between 0.16.8 and 0.16.9, so the 0.16.8 patch applies to 0.16.9 with zero rejects. The fork passively inherits the upstream bytea-COPY correctness fix.Verification —
scripts/sync-upstream.sh 0.16.9 --test@subsquid/ponder@0.16.9-sqd.1biome checkclean; secret-scan cleanScope
published: false— not cutting/publishing a release here; publishing to npm is a deliberate, human-reserved step.0.16.8-sqd.1stays--tag latestuntil then.published:falsebefore the separate publish step).Compat rests on seam-identity + the full suite, as for 0.16.8/0.16.7/0.15.17.