Repository navigation
Fix governed-content revision bindings and release 0.16.36 - #52
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
1 participant
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.
Activation added adoption dates to unchanged approved content, which invalidated retention source bindings and rolled back the write. Source and collection revisions now treat adoption metadata consistently, while approval bindings still use exact Markdown and substantive changes still invalidate reviews.
Preserve published source and whole-schedule approval hashes through exact prior calculations and committed-history checks. Cover atomic and separate activation, rollback, lifecycle changes on Policies, Documents and Training, and Complementary Control dependencies. Release both packages as 0.16.36.
Validation: Node 24 full validation with
CI=true FILEGRC_GLOBAL_TEST_CONCURRENCY=2 npm run validate, focused regressions, browser activation with console/network checks, an isolated representative compliance workspace, a fresh consumer generated with the unreleased local engine, package dry runs, dependency audit, and private-source/secret scans.