Repository navigation
ci: scope release panic probe trust to its checkout - #316
Merged
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.
The manual 0.11.1 release stopped before publication because the Linux FFI panic probe calls Git inside a foreign-owned container checkout. Source selection already handles this ownership boundary, but the later probe starts a separate Git process.
Scope Git safe.directory to the exact GitHub workspace for the panic-probe step. This also lets the manual workflow resume against the existing immutable 0.11.1 tag without modifying tagged release source or relaxing ancestry checks.
Validation: reproduced rejection with Git 2.34.1 in the pinned Ubuntu 22.04 container; the scoped configuration accepts the release checkout while an unrelated foreign-owned checkout remains rejected. All 14 release workflow and preparation tests pass, as do pre-commit script checks. No binary or package changes.