fix(security): promote boundary policy refinements to prod - #200
Merged
Conversation
Co-authored-by: ci-smoke <ci@example.com>
Co-authored-by: ci-smoke <ci@example.com>
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.
Summary
Promote the reviewed public-boundary policy refinements from the default branch to
prodbefore the large current-tip cleanup.Includes only:
Verification
b87b90fe0f2cfefd6a143eee2f033a3da71f54edExpected policy behavior
This is a policy-bootstrap PR. It changes the protected guard itself, and its candidate tip is intentionally still the pre-cleanup public tree. The trusted scan therefore reports both the guard change and the existing private-content findings. Any merge is an explicit, audited administrator exception limited to installing the reviewed policy before the separate cleanup PR.
The following cleanup PR must pass the trusted policy normally; this exception must not be reused for content changes.
Deployment
No deployment. Do not run
redeploy.sh. Do not runrsync --delete.