Skip to content

Use GHCR for the Supabase Edge fixture - #609

Merged
kvz merged 1 commit into
mainfrom
edge-registry
Oct 22, 2026
Merged

kvz merged 1 commit into
mainfrom
edge-registry

Conversation

@kvz

@kvz kvz commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Why: anonymous public ECR pulls hit toomanyrequests: Data limit exceeded before the Supabase Edge fixture can test either SDK package, including main CI attempt 2.

Use Supabase’s official GHCR mirror with the existing v1.76.2 tag and exact SHA-256 digest. Anonymous manifest reads confirmed byte-identical ECR/GHCR indices and the same ARM64/AMD64 images. The integration assertions, coverage and supported package runtimes remain intact.

Fixes #580.

Validation:

  • corepack yarn verify:full on isolated, checksum-verified Node 26.12.1.
  • corepack yarn test:sdk:edge: both packed @transloadit/node and transloadit bundled and ran successfully; no native dependencies, upload budgets and HMAC assertions passed.
  • Council review: no issues found. No new source-text assertions were added for this registry-only change.
  • PR CI: 14 passed, three expected skips. Merged main CI: 15 passed, two expected skips. Both runs passed the actual Edge fixture for both packed SDK packages.

🤖 Claimed by kvz on studio1/node-sdk since 2026-10-22 · resume: codex resume 01a1622a-0fd4-7530-bbcd-ebb3b2800703

@kvz kvz self-assigned this Oct 22, 2026
@kvz
kvz merged commit e4b3769 into main Oct 22, 2026
17 checks passed
@kvz
kvz deleted the edge-registry branch October 22, 2026 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle public ECR throttling in the Edge fixture

1 participant