Repository navigation
Build SDK releases automatically after merging revision requests - #2
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.
Start SDK builds automatically when a reviewed engine revision request is merged to main. Add .github/sdk-release.json selecting the already-tagged private engine commit 8fd3e8780c985721730855396de987e59e268fcf, and resolve that exact revision before launching native Linux, Windows and universal macOS builds.
PR checks validate the request and publication policy without the private-source credential. Only the merged main workflow receives that credential. Existing source cleanup, withheld compiler output, independent SDK audits and all-three-platform publication requirements remain in force. Manual dispatch remains available for retries.
Validation: eight boundary tests pass; actionlint and full public-history audit pass; the actual revision-resolution step emits the expected GitHub job output. No SDK images were built locally. Merging this PR initiates the first native build using ENGINE_SOURCE_TOKEN already configured by the repository owner.