docs(security): #231 remediation plans (RLS lockdown record + storage + realtime-a)#233
Conversation
|
Warning Review limit reached
More reviews will be available in 48 minutes and 49 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Docs-only. Carves the three planning docs out of the #232 draft so they live in
main:rls-lockdown-plan.md— record of the applied prod lockdown + verification checklist.storage-hardening-plan.md— buckets → private + signed URLs + auth uploads plan.realtime-jwt-bridge-design.md— option (a) design (referenced by fix(social): re-fetch realtime messages via decrypting REST + drop dead reactions sub (#124, #231) #230's code comment).The SQL scripts stay in #232 as the applied-to-prod record (not merged). Landing this before #230 resolves #230's doc reference.