Repository navigation
Package scoped operation and native read fixes in Server 1.6.557 - #390
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.
A typed Stack create can succeed while its original scoped Key receives 403 reading the result, because a validated internal ID is parsed a second time. Engine 0.183.357 fixes that resolver and the native ProcessPool metadata identity, while retaining typed public inputs, live actor/Key ceilings and child DENY. This candidate keeps Web Console 1.6.199 and the other component pins.
The publisher now verifies the real protocol on its disposable fresh Server: native pool metadata, unsupported collection input, scoped-Key preview, human-cookie confirmation, one empty Stack create and receipt read, with independent credential/resource cleanup. No Hosts or workloads are created by this gate; full browser acceptance remains separate.
Validation: Engine required CI/CodeQL passed (373 suites, 3,616 tests; zero failures/errors, one existing platform skip). Local related packaging contracts: 47 passed; release-note format: 4 passed; new protocol input guards: 2 passed. Existing VEX exceptions and pending finding contents remain unchanged. Install examples remain on published 556 until publication. Unfinished 8080 workflows and full frontend coverage are explicitly tracked.