docs(migration): Add upgrading information for multiple Sentry packages to TL;DR section #5125
Conversation
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
state that `@sentry/tracing` should be upgraded alongside the used Sentry SDK
lforst
approved these changes
May 18, 2022
size-limit report 📦
|
AbhiPrasad
pushed a commit
that referenced
this pull request
May 30, 2022
…es to TL;DR section (#5125) add a point to the TL;DR section stating that other Sentry packages like `@sentry/tracing` should be upgraded alongside the used Sentry SDK
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.
This mini PR just adds a point to the TL;DR section stating that other Sentry packages like
@sentry/tracingshould be upgraded alongside the used Sentry SDK. Got the idea to add this after I saw that people were just upgrading the SDK to v7 beta but left tracing at v6.