cargo publish verifies the packaged tarball with a full build before uploading, and that build needs a C linker for build-script crates (proc-macro2 was the first to fail). The job's container setup step omitted build-essential, unlike the build and test jobs, so the verification failed with 'linker cc not found' on the v0.1.0 tag.