megadev-release
Megadev release
Ship the disc layout the game was tested with. A bootable ISO alone does not prove that its music tracks, loaded modules or release archive are complete.
Establish the release candidate
Use the project's existing build, content layout, video timing and track numbers.
Pull ewrogers/megadev:latest, limit build containers to --cpus=2, and record the
actual SDK/compiler and source commits. Retain the original-68000 safeguards.
Keep PAL/NTSC timing separate from US/JP/EU boot/security selection; neither is
inferred from a filename. Do not patch a region tag and claim compatibility.
Read the supported disc profile before running
scripts/release.py. Its strict helper targets the current Megadev boot layout,
ISO level-1 data and separate PCM WAV music tracks. Unsupported CUE directives,
raw-sector images and alternate boot layouts need their own verified validator;
do not relabel or silently convert them to pass.