catcrafts.net/.forgejo/workflows
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jorijn van der Graaf c9d2f2d991
All checks were successful
Deploy / build-deploy (push) Successful in 8m44s
CI: build with the beta crafter-build Flatpak, chosen through CRAFTER_REF
Run 533, the first on the Flatpak toolchain, installed the Flatpak, built
the server and passed all 28 suites, then failed building the wasm bundle:
Crafter.Graphics master has used the Shader `defines` and `variant` fields
since 2026-10-06, and the `stable` Flatpak is the 2.1.0 release from three
days before that. Only Crafter.Build master has them, so the toolchain is
its `beta` branch for now, which is also what the rolling `latest` tarball
this job used to download was: a build of master.

The branch is one variable at the top of the job, the way imsd's package
job pins its own (imsd stays on stable; it has no Crafter.Graphics). Flip
it back to //stable once a Crafter.Build release carries the fields. The
wrapper scripts expand the ref at write time, and the install step prints
them along with the Flatpak's branch and commit so a run's log says which
toolchain it used.

Verified locally with beta 2.1.0-10-g4af9280: the wasm bundle builds and
the server suite passes, except ShouldServePostPages, which needs the media
mirror on the deploy mount that only exists in CI.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-16 23:33:06 +02:00
..
deploy.yaml CI: build with the beta crafter-build Flatpak, chosen through CRAFTER_REF 2026-10-16 23:33:06 +02:00