fix(listing): require an authenticated session on sponsor utility endpoints - #1468
fix(listing): require an authenticated session on sponsor utility endpoints#1468rajanpanth wants to merge 1 commit into
Conversation
…points check-slug, email-estimate and featured-posts under /api/sponsor-dashboard/listing are only used from the authenticated listing builder but had no session check. Add a getUserSession gate to each so they aren't callable anonymously, matching the other sponsor-dashboard routes.
|
@rajanpanth is attempting to deploy a commit to the Superteam Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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 |
check-slug,email-estimateandfeatured-postsunder/api/sponsor-dashboard/listingare only called from the authenticated listing builder but had no session check. Adds agetUserSessiongate to each, matching the other sponsor-dashboard routes, so they aren't callable anonymously.Checked all call sites before changing:
featured-posts/email-estimate— relativefetchfrom React Query, browser-side, cookies sent.check-slug—fetchSlugCheckuses plainaxiosrather than@/lib/api, so noAuthorizationheader;getPrivyTokenfalls back to theprivy-tokencookie, so this still authenticates.Happy to adjust if any of these are intended to be public.
pnpm check-typesandpnpm lintpass.