Repository navigation
Fix RFC8785 separator bytes and verify Windows package behavior - #102
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.
MandateBound escaped U+2028/U+2029 despite its RFC8785 proof profile, producing incompatible digests and signatures. Restore literal UTF-8 bytes after existing Unicode validation, verify keys and values against independent byte/signature inputs, and reject legacy escaped proofs without fallback. Document exact-producer historical replay and issuer reissuance requirements for affected artifacts.
Add Windows Node 22.12.0 acceptance for the existing CLI, store, and installed-consumer checks. Exercise both npm command shims from a path containing spaces. Upgrade only fast-uri to 3.1.8 for GHSA-hrr3-gc8f-f4qj; the separate @types/node PR is untouched.
Validation: full Windows Node 24 verification passed (355 passing, six explicit platform skips), including coverage, installed-package acceptance, and offline replay. Independent Node 22 checks passed (57 passing, three explicit Windows symlink skips). Exact candidate source review and privacy/dependency scans passed. Protocol identifiers remain unchanged as a correction to RFC8785 implementation; affected legacy escaped artifacts intentionally fail current integrity checks and require the documented compatibility handling.