fix(ci): Avoid unauthenticated release ref fetch#6
Merged
Conversation
Validate the complete ref snapshot immediately after checkout instead of fetching again without persisted credentials. Keep setup work after validation and make the release fixture fail if another network fetch is introduced. Co-Authored-By: OpenAI Codex <noreply@openai.com>
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.
The release workflow now validates immediately after the full-depth checkout instead of running a second unauthenticated Git fetch. The checkout already fetches every branch and tag, so this keeps the ref snapshot fresh while retaining
persist-credentials: false.The release validation fixture now makes its remote unreachable after populating local refs, covering the reported failure mode and preventing another network fetch from slipping back in.