Skip to content

release.yml: verify the C128 build outputs too #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DNSGeek merged 1 commit into from
Oct 17, 2026
Merged

release.yml: verify the C128 build outputs too #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
Loading