6dfa6ebd15
Baseline PNGs (492, 35 MB) leave git: they now live in the private R2 bucket pcbjam-ci-screenshots as immutable sha256/<hex>.png objects, pinned by the committed screenshot-manifest.json (v2: name, engine, sha256, bytes, dims). tests/baseline-screenshots/ becomes a gitignored cache materialized by the new `npm run screenshots:fetch` (r2-sync.ts + aws4fetch r2-store.ts). - promote.ts: requires the RW keypair (shell env or gitignored tests/.env), syncs the cache, uploads new hashes BEFORE rewriting the manifest; the manifest diff is the only git-visible output. --prune only edits the manifest — R2 objects are never deleted, old commits still resolve. - compare.ts: skips the gate (exit 0, no report.json) when the manifest expects baselines but the cache is empty (secretless callers). - changelog.ts: diffs the manifest between revs and fetches bytes from R2; guards against the migration commit (base manifest not v2 → skip). - gen-manifest --check: v2 schema + resurrection guard (fails if baseline PNGs are ever re-committed); credential-free so every caller can gate. - wasm-build.yml: declares optional read-only S3 secrets, caches + fetches baselines before the lint gate; release.yml/deploy-staging.yml pass them. - screenshot-changelog.yml: triggers on the manifest path instead of PNGs. All 492 objects are seeded and hash-verified in the bucket; fetch/compare degrade to a warn-and-skip without credentials. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
45 lines
1.8 KiB
YAML
45 lines
1.8 KiB
YAML
name: screenshot-changelog
|
|
|
|
# Discord trigger B: when a push to main changes the screenshot manifest (the
|
|
# committed pin of every R2-stored baseline), post an old | new+boxes | heatmap
|
|
# triptych per changed baseline (ADDED image / REMOVED title too). No build, no
|
|
# GPU — it diffs two git revisions of the manifest and fetches the PNG bytes
|
|
# from the R2 CAS bucket (immutable objects, so the old rev's hashes always
|
|
# resolve), so it runs in ~30s. Complements the re-render drift gate in
|
|
# wasm-build.yml (which catches un-blessed renders); this is the human-facing
|
|
# feed of intentional baseline updates as they land.
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
paths:
|
|
- 'tests/screenshot-manifest.json'
|
|
|
|
concurrency:
|
|
group: screenshot-changelog-${{ github.ref }}
|
|
cancel-in-progress: false
|
|
|
|
jobs:
|
|
changelog:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
# HEAD^ is needed to diff the tip commit's manifest changes. (A push of
|
|
# multiple commits reports only the tip commit's baseline diff — fine for
|
|
# a changelog; baseline refreshes are single commits in practice.)
|
|
fetch-depth: 2
|
|
- uses: actions/setup-node@v4
|
|
with:
|
|
node-version: 20
|
|
- name: Install screenshot tooling deps
|
|
working-directory: tests
|
|
run: npm ci
|
|
- name: Post baseline changelog to Discord
|
|
working-directory: tests
|
|
env:
|
|
DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }}
|
|
CI_SCREENSHOTS_S3_ENDPOINT: ${{ vars.CI_SCREENSHOTS_S3_ENDPOINT }}
|
|
CI_SCREENSHOTS_S3_ACCESS_KEY_ID: ${{ secrets.CI_SCREENSHOTS_S3_ACCESS_KEY_ID }}
|
|
CI_SCREENSHOTS_S3_SECRET_ACCESS_KEY: ${{ secrets.CI_SCREENSHOTS_S3_SECRET_ACCESS_KEY }}
|
|
run: npm run screenshots:changelog
|