Repair engine release prerequisites and package test blockers - #1746
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
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.
Release CI required an external Games checkout without provisioning it, and two package tests depended on a stale IK endpoint or external game fixture.
Validation: engine build, ship preflight and focused tests pass;
bun test packages: 7,214 pass, 1 skip, 0 failures. No visual claim: this verifies solver geometry and test independence.Publication is still blocked by existing external Games feel/art-direction failures. Separating SDK publication from those dedicated game-quality gates is pending explicit user approval after automatic review rejected the proposed scope change. No gates have been narrowed.