Repository navigation
fix: check legacy privacy signals and release 0.14.4 - #42
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.
Legacy privacy signals in extension fields currently miss consent and identifier checks. Resolve canonical and legacy GDPR, TCF, US Privacy and EID locations using the selected contract, preserve the original finding paths, and warn on conflicting values. Empty and null canonical values retain precedence. Attribute TCF contradictions to their decoded GPP source when appropriate.
Prepare 0.14.4 and rebuild the committed npm WASM. Add 18 synthetic regression payloads, bringing the dialect manifest to 47 cases, plus privacy integration tests. All 412 workspace tests, formatting and all-target/all-feature Clippy pass. The 34 generated schemas remain unchanged. npm CJS/ESM, packed npm, browser WASM, Worker WASM and native macOS smoke checks pass.
Replay evidence: 47 of 48 stored payloads could be replayed; one ARTF response lacks its request. All 13 added warnings in the replay involve historical redaction placeholders, so the new synthetic fixtures establish the actual privacy behavior. Original consent validity cannot be inferred from redacted data.