Uh oh!
There was an error while loading. Please reload this page.
Restore site embed framing - #1097
Conversation
Deploying with |
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs | tanstack-com | 12a093b | Commit Preview URL Branch Preview URL | Aug 03 2026, 04:09 AM |
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe frame embedding allowlist now permits ChangesFrame embedding allowlist
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Uh oh!
There was an error while loading. Please reload this page.
What changed
Allow the existing
/partners-embedand/sponsors-embeddocuments to bypass the worker's globalX-Frame-Options: DENYheader, alongside the npm stats and Charts embed routes.Root cause and impact
The Cloudflare worker applies
X-Frame-Options: DENYto every response, then removes it only for paths recognized byisFrameEmbeddingAllowed. The two long-standing site embed routes were missing from that allowlist, so browsers refused to render the partner iframe used by the TanStack Start overview. The sponsors embed was broken by the same omission.This restores the intended iframe behavior only for the two explicit embed documents. All regular partner, sponsor, and site pages retain the global frame denial.
Closes#1096
Validation
pnpm testgit diff --checkRisk
Low. The security-header exception is limited to two routes whose sole purpose is iframe embedding, with negative coverage for their normal page counterparts.
Summary by CodeRabbit
New Features
Bug Fixes