Upgrade sentry #2040
Merged
Upgrade sentry #2040
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for @ifixit/commerce-frontendThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! |
Upgrade to v 7.74.0. Expect a bundle size increase that was advertised in 7.73.0. Remove sentry tracing since it was deprecated and it is not necessary anymore
federicobadini
force-pushed
the
upgrade-sentry
branch
from
95cc3f2
to
a4b6234
Compare
|
dev_block 🟥 on merge conflicts Otherwise, the site seems to be working as before 👍 |
|
Conflict resolved |
deltuh-vee
added
QAing
|
Carry Over QA 🎬 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Upgrade to v 7.74.0.
This PR removes @sentry/tracing since it is deprecated and it is not necessary anymore.
A bundle size increase that was advertised in 7.73.0. So if any increase is shown this might be the case.
We are upgrading also because version of Sentry have been associated to errors like the one we are tracking in #1808 - see here. In those case they were build errors, in ours we have runtime errors but the similarity and the fact that the fix was deployed in a newer version wrt the one we are using is worth the try.
QA