Skip to content

feat(chrome): add a starfield layer behind each shader band (#337) #332

feat(chrome): add a starfield layer behind each shader band (#337)

feat(chrome): add a starfield layer behind each shader band (#337) #332

Workflow file for this run

name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
test:
runs-on: ubuntu-latest
services:
# The grounding domain reads/writes real Postgres now (issue #47), and
# npm test's write-path suites (createNode/deleteNode/runSynthesis,
# the MCP create_workspace tool) need a real DATABASE_URL to do that --
# CI never had one, so every one of those has been failing since #47
# landed (issue #56's ##[error] logs, reproduced locally against this
# same ephemeral-Postgres setup: 279/279 pass once a real DB exists).
# An ephemeral service container needs no secret and nobody has to
# provision or pay for a real project just to keep CI green.
postgres:
image: postgres:16
env:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
POSTGRES_DB: postgres
ports:
- 5432:5432
options: >-
--health-cmd pg_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5
env:
DATABASE_URL: postgresql://postgres:postgres@localhost:5432/postgres
steps:
- uses: actions/checkout@v7
- uses: actions/setup-node@v7
with:
node-version: "22"
cache: "npm"
# Node 22's bundled npm (10.x) hard-fails `npm ci` with EBADPLATFORM on
# a properly `optional: true`-marked platform package nested under
# tsx's own esbuild (verified live: the exact same lockfile installs
# cleanly under npm 11 locally) -- a known class of npm bug around
# optionalDependencies resolution, fixed in later npm releases.
- run: npm install -g npm@latest
- run: npm ci
- run: npm run db:migrate
- run: npm run typecheck
- run: npm run lint
- run: npm run check:no-em-dashes
- run: npm run check:generator-count
- run: npm test
- run: npm run build