Repository navigation
feat(organizations): limit sub-org adds to parent members - #8967
Conversation
A sub-organization can invite or add only people who already belong to its parent. The add-member search is limited to active parent members, and accept still requires that membership.
The new catalog key failed i18n parity. Unknown invite rejections already use the generic send error.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe increment correctly restores transient-failure resilience on the post-deploy lease check: the in-flight renewal is still awaited first, then Assumptions: Files Reviewed (3 files)
Previous Review Summaries (3 snapshots, latest commit 8b8a333)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 8b8a333)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe follow-up commit correctly forces a fresh post-deploy lease read, but the new Assumptions: Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
Previous review (commit 897a706)Status: No Issues Found | Recommendation: Merge Executive SummaryThe follow-up commit closes both prior findings: a live-parent check now gates the child-org accept and admin add paths, and Add Member uses a bounded server-side parent-member search that excludes existing child members. No new defects were found in the changed code. Assumptions: Files Reviewed (8 files)
Previous review (commit a5b32bb)Status: 2 Issues Found | Recommendation: Address before merge Overview
Executive SummaryThe parent-membership gating is enforced on invite and admin add, but the accept path never re-checks that the parent organization is still live, so an invitation issued before the parent was deleted can still grant child membership. Assumptions: Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (11 files)
Reviewed by deepseek-flash-latest · Input: 35.9K · Output: 5.6K · Cached: 257.2K Review guidance: REVIEW.md from base branch |
Accept and admin add now reject membership when the parent organization is deleted. Add Member searches a bounded set of live parent members instead of loading the whole parent organization.
An in-flight renewal started during deploy was reused as the post-deploy check, so CI could miss the final pause verification.
The fresh post-deploy read goes through the renewal retry loop after the in-flight renewal finishes, so a single D1 blip does not fail a completed deploy.
iscekic
left a comment
There was a problem hiding this comment.
bot: Reviewed the membership checks, invitation acceptance, parent-member search, and deployment renewal fix. No actionable findings. The focused deployment regression checks pass, and CI is green.
Summary
Test plan