[kylehgc]

The version stamp from #83 broke two of the seven build jobs. Both failures are mine and neither was visible without running it.

Build aarch64-apple-darwin   FAILED   Stamp version from tag
Build x86_64-apple-darwin    FAILED   Stamp version from tag
Build RPM package            FAILED   Generate RPM
Build DEB package            ok
Build x86_64-pc-windows-msvc ok
Build x86_64-unknown-linux-musl ok
Build aarch64-unknown-linux-gnu ok

macOS: two GNU-isms, not one

sed: 1: "Cargo.toml

BSD sed reads the argument after -i as a backup suffix, so the GNU form consumes the script. But fixing that alone would still have failed: 0,/re/ — the address range used to match only the first version = — is also a GNU extension that BSD sed rejects. Uses awk instead, which behaves identically on both.

This is the same mistake as the BSD grep failure in non_utf8_argv_test earlier today: verified against GNU tooling on Windows, shipped to a macOS runner.

RPM: cargo and rpm disagree about -

invalid version "0.1.0-rc.10": contains invalid character
(allowed: alphanumeric, '.', '_', '+', '%', '{', '}', '~', '^')

RPM forbids - in a version; cargo requires semver. The error message names the escape — + is legal in RPM, and semver permits it as build metadata. So the pre-release marker becomes +rc.N:

	0.1.0-rc.10	0.1.0+rc.10
cargo	✅	✅
dpkg	✅	✅
rpm	❌	✅

~ would sort better for both rpm and deb (it orders before the release), but cargo rejects it outright.

Verified

--test                    all 5 tag forms
cargo metadata            0.1.0+rc.10
rpm charset               0.1.0+rc.10 uses only characters rpm's error lists as legal
stamp diff                line 3 only; clap/serde/serde_json intact
stable path               fork-v0.1.0 -> 0.1.0
malformed tag             rejected, manifest untouched

Still unverified

The .deb/.rpm filenames, and BSD awk itself — both need the real runners. The macOS job and the next RC's published assets are the checks worth watching after merge.