Repository navigation
Reconcile provider accounts separately from access grants and release 0.18.9 - #70
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.
Provider account populations were incorrectly required to equal Access Grant counts, which rejects valid reviews containing owned service identities, provider-managed roles, multiple accounts per grant, and inherited identity stores. Add explicit per-source reconciliation so actual retained account rows, permission grants, accountable identities, exclusions, and removals have separate meanings.
The optional model v13 structure retains one rolled-up review and its existing approval. Unknown accounts, missing rows, invalid or expired identities, ineffective owners, unmapped current grants, unrelated proof, and unresolved removals prevent readiness. Inherited identity boundaries require fixed configuration proof and must resolve to a reconciled direct source; sources without an account store cannot conceal grants. A current review renewal records existing human access authorization without inventing historical provisioning dates. Existing records retain their previous checks until explicit reconciliation is adopted.
Fix component Evidence provenance so an authoritative source can retain attachments or external references without pretending to be a rendered page. Nested CLI guides expose object definitions, scaffolds keep actual population decisions blank, and the browser uses the same readiness calculation. No new independent approval or model migration is added. Coordinated patch release: 0.18.9.
Validation:
Released as v0.18.9 at
ce898664ae20c92b921538ef2273f2394ad06b00; merged tree matches final PR head399c67b27cb6d386b13708edcfb3835c07347922. All five required PR checks and main validation passed. Trusted npm publication and installed README smoke passed; both packages report latest0.18.9 with provenance attestations.