seriesoftubes/.github/workflows
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
..
auto-release.yml Release automatically when the version on main changes 2026-10-24 21:54:52 +02:00
ci.yml CI: translation coverage job 2026-10-26 06:04:28 +01:00
claude.yml Answer @claude mentions on issues and PRs, including PRs from forks 2026-10-27 07:01:38 +01:00
perf-comment.yml Performance benchmark on a big network, posted on every PR 2026-10-26 06:39:23 +01:00
perf.yml Fewer merge conflicts: actions by area, one city per line, sorted dictionaries 2026-10-27 10:10:16 +01:00
release.yml Regenerate published weekly puzzles when a release's prices break them 2026-10-29 10:03:20 +01:00
weekly-puzzle.yml Regenerate published weekly puzzles when a release's prices break them 2026-10-29 10:03:20 +01:00