chore(ci): bump forge-base to v0.2.3 (Playwright browser cache) #1113

Merged

charles merged 1 commit from chore/forge-base-v0.2.3 into main

2026-05-11 20:54:23 +00:00

claude-desktop commented

2026-05-11 20:40:03 +00:00

Collaborator

Summary

Bumps forge-base reusable workflow + container image from v0.2.2 to v0.2.3.
forge-base v0.2.3 adds an actions/cache step for ~/.cache/ms-playwright in qa-bun.yml. apps/web's Vitest browser-mode setup downloads ~170MB of Chromium during just ci-setup; warm cache makes that a no-op.
Cache key includes bun.lock hash → a Playwright version bump invalidates and re-downloads automatically.

Changes

.forgejo/workflows/qa.yml:
- uses: …/qa-bun.yml@v0.2.3 + image_tag: v0.2.3 on the reusable qa job.
- Inline image: bumps for db-schema, dockerfile, i18n-string-check, sql-layer-check jobs (all use the same forge-base/bun image).
release.yml left at v0.2.1 — unrelated to Playwright caching, separate bump if desired.

Test plan

First post-merge QA run downloads Chromium (cold cache) — same wall-clock as today.
Second QA run on the same bun.lock hits the cache (Cache restored from key: playwright-v0.2.3-… in job log) and playwright install no-ops on the browser binary.
db-schema, dockerfile, i18n-string-check, sql-layer-check jobs still pass on the new image (no behavioural diff vs. v0.2.2; same base image rebuilt).

## Summary - Bumps `forge-base` reusable workflow + container image from `v0.2.2` to `v0.2.3`. - forge-base v0.2.3 adds an `actions/cache` step for `~/.cache/ms-playwright` in `qa-bun.yml`. apps/web's Vitest browser-mode setup downloads ~170MB of Chromium during `just ci-setup`; warm cache makes that a no-op. - Cache key includes `bun.lock` hash → a Playwright version bump invalidates and re-downloads automatically. ## Changes - `.forgejo/workflows/qa.yml`: - `uses: …/qa-bun.yml@v0.2.3` + `image_tag: v0.2.3` on the reusable `qa` job. - Inline `image:` bumps for `db-schema`, `dockerfile`, `i18n-string-check`, `sql-layer-check` jobs (all use the same `forge-base/bun` image). - `release.yml` left at `v0.2.1` — unrelated to Playwright caching, separate bump if desired. ## Test plan - [ ] First post-merge QA run downloads Chromium (cold cache) — same wall-clock as today. - [ ] Second QA run on the same `bun.lock` hits the cache (`Cache restored from key: playwright-v0.2.3-…` in job log) and `playwright install` no-ops on the browser binary. - [ ] `db-schema`, `dockerfile`, `i18n-string-check`, `sql-layer-check` jobs still pass on the new image (no behavioural diff vs. v0.2.2; same base image rebuilt).

claude-desktop added 1 commit

2026-05-11 20:40:03 +00:00

chore(ci): bump forge-base to v0.2.3 (Playwright browser cache)

qa / i18n-string-check (pull_request) Successful in 22s

Details

qa / dockerfile (pull_request) Successful in 23s

Details

qa / sql-layer-check (pull_request) Successful in 11s

Details

qa / db-schema (pull_request) Successful in 55s

Details

qa / qa-1 (pull_request) Successful in 9m55s

Details

qa / qa (pull_request) Successful in 0s

Details

590482b428

forge-base v0.2.3 adds a cache step for ~/.cache/ms-playwright in
qa-bun.yml, so apps/web's Vitest browser-mode setup skips the
~170MB Chromium download on subsequent runs (key invalidates when
bun.lock changes).

Bumps both the reusable-workflow @ref and the image_tag input to
v0.2.3, plus the inline `forge-base/bun` container image used by
the project-specific db-schema, dockerfile, i18n-string-check and
sql-layer-check jobs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

charles merged commit e64445626e into main

2026-05-11 20:54:23 +00:00

charles deleted branch chore/forge-base-v0.2.3

2026-05-11 20:54:23 +00:00

charles referenced this pull request from a commit

2026-05-11 20:54:24 +00:00

chore(ci): bump forge-base to v0.2.3 (Playwright browser cache) (#1113)