Repository navigation
Fix release request startup and retry native SDK builds - #3
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 first merged release run stopped in revision resolution with ModuleNotFoundError: release: GitHub executes shell:python blocks from a temporary script directory, so they do not import modules from the checkout as python -c did locally. No private source checkout, compilation or artifact upload ran.
Resolve requests through the existing release.py command entry point invoked from bash, emitting only the exact commit=SHA GitHub output record. Add a subprocess regression covering the real command from a separate directory, manual overrides, generic failures and invalid requests. Add an optional positive attempt field so a reviewed PR can retry the same unpublished revision without moving its source tag; request attempt 2 for the existing engine revision.
Validation: nine publication-boundary tests pass; actionlint, staged-content and complete-public-history audits pass. PR CI has no source credential. Merging this PR automatically retries the three native SDK builds with the existing source secret. SDK images are built only by CI.