Update Sentry version #566
Open
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
Fixed support for hpt file type and added stage CI/CD pipeline.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Update Sentry dependency (fixes issues related to the conflict of the Sentry SDK v8+)
What is the current behavior? (You can also link to an open issue here)
In the Sentry v7-v8 the @sentry/hub was merged with @sentry/core and than the
__SENTRY__.hubwas completely removed. The @sentry/minimal has not been updated for a long time and uses__SENTRY__.hub.isOlderThan()method failing with the error of missing variable.What is the new behavior (if this is a feature change)?
Instead of @sentry/minimal it uses @sentry/core that is aware of new SDK version and uses it without throwing exceptions.
Other information:
—