Weekly puzzle: tests, CHANGELOG, architecture and deploy notes
This commit is contained in:
parent
2ac9143db9
commit
587d50decf
5 changed files with 284 additions and 1 deletions
|
|
@ -40,6 +40,14 @@ publishes the GitHub release and starts `release.yml`: test, `REQUIRE_NOTES=1 np
|
|||
`pages: write`. Pushes to `main` and pull requests build but never deploy. The `release` skill has the
|
||||
steps.
|
||||
|
||||
**The one exception: the weekly puzzle.** Every Sunday at 03:37 UTC `weekly-puzzle.yml` commits the new
|
||||
`site/puzzles/weekly/<key>.json` to `main` (data only, no version bump) and starts `release.yml` for the **live
|
||||
release tag** with `weekly=true`. That run rebuilds exactly the live release, with every weekly file from `main`
|
||||
added, checks them with `scripts/weekly-puzzle.js --check`, and deploys it in the same `pages` concurrency group.
|
||||
Players get no update banner (the version does not change). Every release build also copies all weekly files from
|
||||
`main`, so a release never drops a published week. Weekly files are plain JSON the game fetches only when the
|
||||
Puzzles list opens and never trusts; the service worker serves them network-first. See `docs/ARCHITECTURE.md`.
|
||||
|
||||
## Before you hand back a change that touches the build, deploy or loading
|
||||
|
||||
```bash
|
||||
|
|
|
|||
|
|
@ -12,6 +12,15 @@ that version's CHANGELOG section as notes, and dispatches `release.yml`, which b
|
|||
to GitHub Pages (https://seriesoftub.es). GitHub Pages is the only host, ever: see the
|
||||
`github-pages` skill.
|
||||
|
||||
## Weekly puzzles are not releases
|
||||
|
||||
`weekly-puzzle.yml` publishes a new puzzle every Sunday morning without a release: it commits the JSON under
|
||||
`site/puzzles/weekly/` to `main` and redeploys the live tag through `release.yml` (`weekly=true`). Never bump the
|
||||
version for a weekly puzzle. To publish or fix one by hand: `node scripts/weekly-puzzle.js --key 2026-W45 --force`,
|
||||
`node scripts/weekly-puzzle.js --check`, commit to `main`, then run the "Weekly puzzle" workflow (or
|
||||
`gh workflow run release.yml --ref <live tag> -f tag=<live tag> -f weekly=true`). A release includes every weekly
|
||||
file on `main` when it builds.
|
||||
|
||||
## Only release when Frederic says so
|
||||
|
||||
Never bump the version on your own. Finished work is committed and pushed with its
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue