Repository navigation
Publish the portable core without widening the source boundary - #6
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.
Publish the portable core required by Vagrant’s renderer-independent content decoders. Allow only the two named WolEngine.Core.dll files and their reference props; apply the existing managed PE/debug-directory checks to the core DLLs as well. Core source, symbols, extra DLLs and private build output remain rejected.
Request the exact tagged engine revision dcb5145dfeb3906830c0c6dc6b6d1f22ad1b4950 from wol-engine PR #152. Merge the engine change first, then this release request: native Linux, Windows and macOS CI builds and independently audits all three SDKs before publication. The source token and compiler-log boundary are unchanged.
Validation: all 12 policy tests pass, including new portable-file, disguised-source, extra-binary and embedded-symbol rejection cases. No distribution images were built locally. Vagrant will download and vendor the published assets after this workflow succeeds.