fix: preserve selected release execution - #23
Merged
Conversation
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.
Summary
successRoot cause
Recovery run 30357111315 verified the immutable release and passed
select-release, but GitHub propagated the intentionally skipped Release Please ancestry into jobs with plain conditions. Build, live smoke, publication, and registry verification all skipped while the workflow reported success.Impact
A successful verified selector now reaches build on the first attempt. Cancellation, reruns, failures, skipped direct dependencies, and missing dependency results remain fail-closed.
Verification
uv lock --check