Repository navigation
fix: allow Sentry Replay workers in CSP - #24
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 10 included reviews per hour; 5 remain after this review. 📝 WalkthroughWalkthroughThe deployment Content-Security-Policy now allows same-origin and ChangesWorker CSP policy
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The PR narrowly permits Sentry Replay workers while keeping blob scripts forbidden and preserving Vercel/nginx CSP parity. No actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
Comment |
Outcome
Allows Sentry Replay's privacy-masked compression worker without allowing blob scripts or weakening the rest of the production CSP.
Changes
worker-src 'self' blob:to the synchronized Vercel and nginx CSPsVerification
nginx:alpineLive reproduction
Production emitted a CSP error for a Sentry Replay blob worker because
worker-srcwas absent and Chrome fell back toscript-src. The new directive is scoped to workers;script-srcstill excludesblob:.CI note
GitHub Actions currently cannot allocate runners because the account is out of Actions minutes. Local current-head checks cover this three-file CSP change; Vercel preview will provide the real browser verification.
Summary by CodeRabbit
Bug Fixes
Tests