From 3c1cb76fb5d2b8d45df0b37d5bc9c47c3aac7688 Mon Sep 17 00:00:00 2001 From: DNSGeek Date: Sat, 17 Oct 2026 11:36:19 -0700 Subject: [PATCH] release.yml: verify the C128 build outputs too The release job's verify step predates the C128 port and only checked the C64 PRGs, although the same make_petproject.sh run puts the C128 set and its boot sector on the released disk. Add the C128 checks build.yml already runs so a C128-only breakage fails the release instead of shipping. Co-Authored-By: Claude Fable 5.1 --- .github/workflows/release.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 536c082..f966166 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -38,7 +38,16 @@ jobs: for m in modasm moddet moddis moddsk modren modtok modsfr modsct modscr modscrh; do test -s "build/${m}.prg" done - echo "All PRGs and the disk image are present." + # The default build also carries the C128 set and its boot sector + # on the same disk, so a C128-only breakage must fail the release + # too (same checks as build.yml). + test -s build/c128/editor.prg + for m in modasm moddet moddis moddsk modren modtok modsfr; do + test -s "build/c128/${m}.prg" + done + test -s build/c128/boot128.bin + head -c 3 build/c128/boot128.bin | grep -q CBM + echo "All PRGs (C64 + C128), the boot sector and the disk image are present." - name: Stamp versioned disk image run: cp petproject.d64 "petproject-${GITHUB_REF_NAME}.d64"