Repository navigation
Apply approved retention rules to Source Coverage in 0.20.0 - #84
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.
An owner can apply an unchanged independently approved retention rule to an explicit Source Coverage population. The decision binds the exact source, population, approved Information Types, purpose, cutoff, disposal and holds. Retention readiness and source preparation use the same resolution, so actual retrieval proof plus a valid owner application no longer asks for another approval of the unchanged schedule. Raw source expiration remains separate from retained control proof.
Release both packages as 0.20.0 because older readers reject the added scope relationship. Model v13 remains unchanged in version, with no migration. Core 0.20 supports existing 0.18 and 0.19 repositories; recording a Source Coverage application requires an explicit 0.20 manifest and lockfile adoption. Existing service application fingerprints, historical approvals and nonmaterial amendments stay valid.
Validation: independent code/security reviews found no remaining issues; 44 focused tests passed; full Node 24 validation passed; generated consumer validates 224 records with zero errors or warnings; both package dry runs, dependency audit and private-data scan passed. Local Playwright verified selection, successful save, unchanged approved rule, and stale-source rejection with inspected screenshots, browser/network output and server logs.