Repository navigation
Fix program-wide Access Review completion and release 0.20.2 - #86
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.
Unscoped Access Review occurrences could not accept native completion records because workspace membership required an unsupported Obligation field. Native results now match the unscoped workspace member while preserving Program membership, activity identity, dates, results and explicit population checks.
Program-wide Access Reviews share the baseline's complete provider, grant-decision and source-proof assessment. Planner, validation, CLI, browser, readiness and audit paths recover unchanged committed reconciliations from their dated Git facts, so later provider or grant changes do not reopen completed work. New or edited reconciliations still use current scope and proof.
Reject unsupported
reconcile-obligation --previewbefore any write, with a no-source-change regression.Release coordinated packages as 0.20.2. Existing date-sensitive test fixtures now use consistent workspace dates across UTC midnight.
Validation: Node 24 clean install and
CI=true FILEGRC_TEST_CONCURRENCY=2 npm run validate(complete suite, two local workers); 14 new regression tests; real browser acceptance and wrong-type rejection on a fresh local instance; fresh consumer generated with local 0.20.2 (224 resources, zero errors/warnings); package dry runs and npm audit. Combined code and security review completed.