Skip to content

Build SDK releases automatically after merging revision requests - #2

Merged
JBailes merged 1 commit into
mainfrom
ci/release-requests
Nov 15, 2026
Merged

JBailes merged 1 commit into
mainfrom
ci/release-requests

Conversation

@JBailes

@JBailes JBailes commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

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.

@JBailes JBailes changed the title Start SDK releases when reviewed revision requests are merged Build SDK releases automatically after merging revision requests Nov 15, 2026
@JBailes
JBailes merged commit 1e3f6f7 into main Nov 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant