Commit graph

11 commits

Author SHA1 Message Date
Frederic Jung
d03dde6fcd
Release deploys again when its tests were skipped on purpose
A skipped job skips every job that needs it, even through one that runs
anyway: since auto-release passes tested=true, the tests job is skipped,
build ran with always(), and deploy (no condition of its own) was skipped.
v3.2.0 built and never went live. Deploy and IndexNow now run whenever
the job before them succeeded.
2026-11-07 14:38:19 +01:00
Frederic Jung
4e6f780c81
No double runs in a release: container test and weekly tests once
A version bump's push started docker.yml's test, then auto-release
started docker.yml again for the tag, which tests the same code before
it publishes: the push skips its test while the version is not tagged.
The deploy re-ran the weekly-puzzle tests even when main's weekly files
are the tag's own, which CI had just tested: it now runs them only for
files that differ (a newer or refitted week) or an untested tag.
2026-11-07 10:28:57 +01:00
Frederic Jung
0342d90657
Faster tests, split everywhere: one sharded CI for pushes and releases
- The harness builds the DOM without the page's 2 MB of script text and
  runs the scripts straight in the window: a page load in tests takes
  about half the time (jsdom's parser was slow on the script text).
- That also took the game's source out of the DOM, which showed three
  tests that matched a phrase in the page source rather than the screen;
  they now check the panel, the routing window and the dictionary.
- CI plans its split once and runs the tests on 6 runners; every run on
  main records each file's time and caches it, so the parts stay even
  without anyone refreshing tests/durations.json.
- auto-release.yml and release.yml call the same sharded tests instead
  of running all 170 files on one runner each (11 and 15 min); a release
  is tested once, before it is tagged.
- Audit: five tests that duplicated a gameplay rule or checked nothing
  are gone; the two slowest checks sample a third of the cities, and a
  year of play to reach one due date became a moved due date.
2026-11-07 07:24:09 +01:00
Frederic Jung
98735eb769
Container image: releases only, a token by default, lean layers; every action pinned
The image is published to GHCR as the release's version when a release
dispatches docker.yml, and never as latest or per commit. Pushes and pull
requests that touch it build it and try headless (with and without a
token) and browser mode, without publishing.

The image: node:24-slim pinned by digest (the major CI tests on), npm ci
from the lockfile in its own layer, only src, site, scripts and the
harness copied in (an allow-list .dockerignore), root-owned and run as
node, /saves ready for --save-dir. The entrypoint runs the servers with
node directly and, with no SOT_MCP_TOKEN, makes a token for the run and
prints it (MCP_NO_TOKEN=1 to opt out); the docs publish ports to
127.0.0.1 and explain --allow-host. Labels, SBOM and provenance on push.

Every GitHub Action in every workflow is pinned to a commit SHA with its
version, and Dependabot keeps the actions, the image's base and the npm
tools current. tests/docker.test.js guards all of it. The ADR and the
github-pages skill say the image is a tool: GHCR only, never Pages.
2026-11-05 20:14:04 +01:00
Frederic Jung
4e6e8294d2
Architect runs: a generated run every week
scripts/weekly-architect.js picks an HQ in a region the last weeks did not have and
designs each brief against the network a reference architect has built so far, so
every brief asks for something new; the game's own checklist and chaos monkey review
judge it, and the whole run is replayed from the file for three stars. The game
fetches architect/weekly/<key>.json when Puzzles opens, checks it field by field and
writes the briefs' text itself. The Sunday job and the release deploy carry it like
the weekly puzzles and scenarios. Later briefs' cities no longer show early.
2026-10-30 13:44:04 +01:00
Frederic Jung
0ece48a79d
Ship weekly scenarios with the weekly puzzle run; docs and skills 2026-10-29 17:34:38 +01:00
Frederic Jung
7cbe0ec09b
Regenerate published weekly puzzles when a release's prices break them
--check now re-solves every week not over yet and, when its budget no longer
verifies, regenerates it deterministically: the same puzzle with a new budget
if that works, else a fresh one for the key. A regenerated file carries rev 2,
3...; the game keeps stars per revision, so only that week's stars reset.
Past weeks are left alone unless the game rejects them. release.yml runs it
before the tests on every deploy, weekly-puzzle.yml before making the new
week; either fails only if a week cannot be regenerated.
2026-10-29 10:03:20 +01:00
Frederic Jung
2ac9143db9
Weekly puzzle workflow: Sunday 03:37 UTC, commit the data to main, redeploy the live release with it through release.yml; releases ship every weekly from main 2026-10-28 20:44:28 +01:00
Frederic Jung
c59be2d16d
Release automatically when the version on main changes
A new auto-release workflow runs the tests, tags v<version>, publishes a
release with that version's changelog section and starts the deploy from
the tag. It skips versions that are already tagged and refuses older
versions or ones without notes.
2026-10-24 21:54:52 +02:00
Frederic Jung
494d71793e
Fix map wrap, touch and keyboard input; harden build and release workflow; docs 2026-10-23 17:56:34 +02:00
Frederic Jung
1685a045e6
Series of Tubes 1.0.0
A cartoon browser game about building the internet, deployed to
https://seriesoftub.es from published releases only.

- site/: the single-file game plus favicons, app icons, manifest,
  social image, robots.txt, sitemap.xml, llms.txt and a 404 page.
- Full SEO head: canonical URL, Open Graph and Twitter cards,
  WebSite and VideoGame structured data, noscript fallback.
- Cookieless Ridiculytics analytics via stats.seriesoftub.es, pinned
  with SRI and active only on the production domain.
- Headless test suite (node:test + jsdom), CI on every push, and a
  release workflow that verifies the tag, tests, builds, deploys to
  GitHub Pages and pings IndexNow.
2026-10-23 09:01:39 +02:00