Repository navigation
release: the promote step tests each platform's archive by name - #997
Merged
Merged
Conversation
…f both names failed under pipefail for the absent one
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
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.
The promote step of release.yml listed
mcpp-<v>-<platform>.tar.gzand.zipwith onelsand piped it togrep -q .. Underset -euo pipefailthelsof the absent name fails the pipeline, so every platform was reported as holding no archive, and the tag push of v2026.11.21.1 (run 44936964201) ended there although the verified run (44930053323) holds all four archives. Each name is now tested with[ -f ]. After the merge,release.ymlis dispatched withtag=v2026.11.21.1: the tag's tree is the verified one, so its archives are promoted.