Skip to content

Publish the portable core without widening the source boundary - #6

Merged
JBailes merged 1 commit into
mainfrom
release/portable-core
Nov 15, 2026
Merged

JBailes merged 1 commit into
mainfrom
release/portable-core

Conversation

@JBailes

@JBailes JBailes commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

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.

@JBailes JBailes changed the title Audit and publish portable core binaries with the engine SDK Publish the portable core without widening the source boundary Nov 15, 2026
@JBailes
JBailes merged commit a6e4441 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