fix(release): bump hard-coded version strings to 0.0.2#13
Merged
Sunrisepeak merged 1 commit intomainfrom May 8, 2026
Merged
Conversation
…h MCPP_VERSION
The v0.0.2 release.yml run produced a fully-functional musl-static
binary, but the smoke-test step rejected it because `mcpp --version`
still printed `mcpp 0.0.1`. The version literal had been hand-coded in
four places that the [package].version bump in mcpp.toml didn't reach:
- src/toolchain/fingerprint.cppm:21 MCPP_VERSION = "0.0.1"
- src/cli.cppm:64 "mcpp v0.0.1 — ..." (print_usage)
- src/cli.cppm:2805 "mcpp 0.0.1" (cmd_self_version)
- src/cli.cppm:2874 "mcpp 0.0.1" (--version handler)
- src/cli.cppm:2947 .version("0.0.1") (cmdline App ctor)
Bump the canonical constant in `fingerprint.cppm` to 0.0.2 and refactor
all five sites to read `mcpp::toolchain::MCPP_VERSION` so future bumps
only need a one-line change. The fingerprint constant already drives
the toolchain hash key, so its value matters for cache invalidation
anyway — this consolidates "what version am I" into a single
authoritative location.
Verified locally:
$ mcpp --version
mcpp 0.0.2
$ mcpp self version
mcpp 0.0.2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The v0.0.2 release.yml run produced a fully-functional musl-static
binary, but the smoke-test step rejected it because
mcpp --versionstill printed
mcpp 0.0.1. The version literal had been hand-coded infive places that the
[package].versionbump inmcpp.tomldidn'treach.
Bump the canonical constant
mcpp::toolchain::MCPP_VERSIONto0.0.2and route every other
mcpp 0.0.xprint site through it. Future bumpsneed a one-line change.
Test plan
mcpp --version→mcpp 0.0.2mcpp self version→mcpp 0.0.2