Repository navigation
Fix Unicode source spans in the public privacy gate (v0.24.1) - #28
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.
Fix UTF-8 source-span normalization in the fixed build-policy declaration. Python AST positions are byte offsets; the privacy gate now applies them to UTF-8 bytes, preserving neighboring source content when a multibyte prefix appears on the same line.
Positive and negative Unicode-prefix controls cover the corrected boundary. Existing rule categories and the narrow owned-policy exception remain enforced. This prepares v0.24.1; installer behavior, media modules, public capability limits, and the bundled Cleanup source are unchanged.
Validation is recorded locally and in the required six-platform/Python matrix plus reproducible-release job. Merge and release require all exact-head checks to succeed. The owner requested publication; retain the documented owner maintenance exception, exact tested tree, and unchanged protections. No independent approving review, live-account acceptance, signed-update assurance, or zero-REVIEW whole-product closure is claimed.