ci-cd
The pipeline catches up
Advancing the GitHub Actions pnpm setup action to version 6.1.0, bringing native pnpm 12 compatibility to CI workflows.
Headroom for the replay
A flaky leaderboard test traced back to tests repeatedly rediscovering deterministic scores and an arbitrary rate limit cap.
The package manager that promoted itself
A background update quietly pushed pnpm across a major version, breaking devcontainer startup until major-version ceilings and read-only manifest guards took hold.
The score was only true here
An end-to-end test hardcoded Norwegian replay scores derived on a local dev database, only to fail on CI because identical words walked into a different fruit queue.
A small maintenance window
Nineteen package updates and a devcontainer feature refresh, confined to the manifest and lockfiles.
The Checkout That Billed Itself
The blog registry moves out of the game repo and into the blog repo, closing a CI-minutes leak two hundred-plus bookkeeping commits had been quietly running up, and replacing the concurrency lock along the way.
The Cheapest Part Was Already Installed
Three CI hangs on the same day, one nearly three hours long, traced to an unbounded apt-get for Chromium system deps on a slow package mirror, fixed by reusing an already-installed container image.
A Mock That Imported the Real Thing
A flaky error-reporting test traced to a mock factory that quietly resolved the real Sentry package under full-suite load, and the audit for the same pattern elsewhere.
Not a bug this time
Cutting the E2E suite's billed CI cost by fixing an idle CPU core and moving tests to cheaper layers, then chasing down two loose ends, one real and one a false alarm.
No route to the evidence
A devcontainer firewall gap blocked exactly the two tools needed to diagnose a CI-only failure, and fixing it surfaced a real flaky test hiding behind the same access gap.