ci(cpp): remove the alpha pre-release publish flag - #53
Merged
Conversation
Companion to the Rust change: #40 flipped the C++ `alpha` default to false, and the flag has no remaining use. It was unreachable from the release pipeline (`publish_artifacts.yml` never forwarded it), it is not what makes re-runs safe (the `tag_exists` precheck already skips a tag that exists), and it cannot fix a bad final release since `x.y.z-alpha.N` sorts below `x.y.z`. Drop the input from all four C++ publish workflows, collapse the version resolution to the spec version, and delete `next_alpha_version.sh`. Also tighten the version grammar in the shared helpers now that no pipeline can produce a pre-release: `tag_exists.sh` (used by both the Rust and C++ leaf workflows) and `vcpkg/bump_port.sh` now accept only `x.y.z`, and the `cpp_registry.yml` input examples no longer show an alpha version.
andrew-coleman
approved these changes
Jul 31, 2026
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
2 participants
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.
What
Companion to #41, doing the same for C++: delete the
alphainput fromcpp_publish.yml,cpp_protobuf.yml,cpp_antlr.yml, andcpp_extensions.yml, collapse version resolution to the spec version, and deletescripts/cpp/next_alpha_version.sh.#40 already flipped the C++ default to
false; this removes the flag.Why the flag can go entirely
publish_artifacts.ymlnever forwardedalpha, so it was only settable via a manualworkflow_dispatch.tag_existsprecheck already skips pushing a tag that exists — and for C++ the tag is the publish.x.y.z-alpha.Nsorts belowx.y.zin semver.Shared helpers
Now that no pipeline can produce a pre-release, the version grammar in the shared helpers is tightened to
x.y.zonly:scripts/tag_exists.sh— used by both the Rust and C++ leaf workflowsscripts/vcpkg/bump_port.sh— plus its usage example and REF-line commentscpp_registry.yml— theversioninput examples no longer show0.96.0-alphaMerge order
Please merge #41 first.
tag_exists.shis shared, so if this lands first it would reject an alpha tag while the Rust workflows could still request one. Nothing in the release pipeline exercises that path, but the ordering keeps it consistent.Notes
cpp/*/v*-alphatags and the vcpkg registry entries pinned to them are left as-is.scripts/tag_exists.sh:21has a pre-existing shellcheckSC2086(unquoted$TAG_NAME) that I left alone as out of scope.🤖 Generated with AI