Repository navigation
Apply approved retention rules to new services; release 0.19.2 - #82
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.
Applying an already approved retention rule to a new service previously invalidated the whole schedule review. Owners can now record a dated service-applicability decision against the exact independently approved rule, preserving that approval when the complete rule fits.
The shared CLI, browser and readiness checks bind purpose, cutoff, disposition, holds, duties, governing sources and service/provider scope. Material rule or category changes still require independent review. Applications are immutable, support dated retirement, and appear in periodic schedule oversight. Existing model 13 workspaces can adopt these optional records after upgrading the dependency and lockfile; hosted runtimes must upgrade before new records are published.
Release 0.19.2 coordinates both npm packages. Validation includes the full Node 24 release suite, focused historical/authority/immutability tests, real-browser fit rejection and successful save, inspected screenshots, a fresh generated consumer, package inspection and npm audit.