feat: enable Sentry back#2550
Merged
ludovicm67 merged 4 commits intomainfrom Apr 27, 2026
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This enables Sentry back, using the v7 of
@sentry/nextjs, like it was done previously on 71c1285.Many of the changes were ported back from that commit as well.
I added a way to configure CSP on the fly in case it doesn't point to sentry.io ; this could be done using
NEXT_PUBLIC_SENTRY_CSP.#2541 was an attempt using the v10 of the module, but our Next.js version is too old.
I'm closing #2541 in favor of this PR, as the upgrades would be done with the rest in future PRs.