Repository navigation
Preserve operating content across governed revisions - #103
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.
Returning active governed content to draft or approving its next revision could discard the in-force baseline, reopen completed acknowledgments and source readiness, or erase earlier calendar debt. Resolve the last valid committed edition until actual cutover across scheduling, readiness, period checks, retention applicability and evidence packets, using that edition’s exact JSON, Markdown and approval/activation proof.
Keep current proposals and live inventory facts visible. Invalid claimed cutovers, stale proof, retirement, material source changes and true rule cutovers remain actionable. The retention application dialog shows the approved rule being applied, and packets include explicit operating snapshots alongside current source proposals.
Request-scoped proof/history reuse removes repeated Git and collection calculations. Full and sectional app-state reads share one assessment cache after acquiring the mutation lock, which prevents per-rule proof recalculation while preserving next-request freshness. On a 764-resource workspace, workflow completed in 58.62 seconds versus 72.59 seconds for 0.21.8, with identical work items and assessment statuses.
Validation: all five required checks passed for final head 2315761, including full clean-install Node 24 validation and Ubuntu Node 20/22, macOS Node 24 and Windows Node 24 compatibility. Isolated macOS full validation passed on 2648e73 with identical published package bytes; all 24 final script tests passed separately on final head 2315761. The final intervening change only handles the Linux process-exit inspection race. Fresh combined code/security reviews, 100 focused state/cache cases, actual browser Policy/Training/schedule/Source Coverage/calendar paths, and the hosted consumer’s 131 browser tests passed. A 764-resource consumer passed validation, readiness and workflow checks; its static build completed in 132.58 seconds. Package inspections, fresh consumer checks and npm audit passed with zero vulnerabilities. Model 13 and the existing 0.21.6 source-feature minimum stay unchanged.
Released as v0.21.9 from
ae25bb4514f1be995a8ed301231bc17a58a756e7. Protected validation and publication, provenance and README smoke passed. Both npm packages are installable aslatest; verified registry signatures and attestations bind their exact package digests to this release.