Repository navigation
Preserve completed partial windows across later content activation - #78
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.
Reactivating governed content after a completed initial partial window had ended made that unchanged occurrence fail validation. The validator preserved committed partial windows only while the later cutover still overlapped them.
Preserve an exact Git-bound partial window even when a later content cutover falls after its end. New windows still require overlap, and rule, owner, key, cutoff, population and coverage validation remain in place. No completed records or dates are rewritten.
Focused regression coverage includes a closed partial window, rejection before historical commitment, and rejection of an edited historical start. Two independent combined code/security reviews are clean. A fresh consumer validates, both package dry runs pass, and npm audit reports no vulnerabilities. Coordinated patch release 0.18.15, no model migration.