build(deps): Bump sentry-android from 3.1.3 to 3.2.0 in /android #1208
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
|
@dependabot rebase |
93d7289 to
8bdc2b8
Compare
Bumps [sentry-android](https://github.com/getsentry/sentry-java) from 3.1.3 to 3.2.0. - [Release notes](https://github.com/getsentry/sentry-java/releases) - [Changelog](https://github.com/getsentry/sentry-java/blob/main/CHANGELOG.md) - [Commits](getsentry/sentry-java@3.1.3...3.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
8bdc2b8 to
25b197a
Compare
mergify bot
pushed a commit
to celo-org/celo-monorepo
that referenced
this pull request
Dec 19, 2020
### Description Upgrade sentry/react-native from 1.7.1 to 2.1.0. This is part of our effort to improve debugging capabilities. With this update we hope to see better stack traces in some native crashes where the entire trace is missing. I went through the release notes for each of the releases since 1.7.1 to make sure we capture any breaking changes and to see what has been fixed and what to watch out for. One thing that has been added is release health which we should discuss whether we want on or off: https://blog.sentry.io/2020/05/19/crash-free-sessions-carefree-users-with-release-health What's new in sentry: - Bump sentry-android to 3.2.0 getsentry/sentry-react-native#1208 - Fix: set userId for hard-crashes if no user is set [#1049](getsentry/sentry-java#1049) - Bump @sentry/javascript dependencies to [5.28.0](getsentry/sentry-react-native#1228) - Bump sentry-cocoa to [6.0.9](getsentry/sentry-react-native#1200) ### Other changes Set sentry automatic session tracking explicitly off because the default has changed in 2.0. Not sure yet if we want that on so I set it off to be explicit. ### Tested Manually causing crashes in JS: `throw new Error("My first Sentry error!");` and in native: `Sentry.nativeCrash();` ### Related issues - Fixes #6203 ### Backwards compatibility Yes.
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.
Bumps sentry-android from 3.1.3 to 3.2.0.
Release notes
Sourced from sentry-android's releases.
Changelog
Sourced from sentry-android's changelog.
Commits
e0bd26achore: 3.2.0b98169afeat: expose a module loader for Android thru sentry-native (#1043)26f4693fix: Clean up JNI code and properly free strings (#1050)01cfbfeFix: userId should be set for hard crashes (#1049)f98e258Sentry NDK integration is compiled against default NDK and CMake versions bas...ae8c568fix changelogf43edb9Configurable SentryExceptionResolver Order for getsentry/sentry-java#681 (#1008)94691a2Resolve HTTP Proxy parameters from the external configuration. (#1035)bcbd5c5Add java doc based on sentry-data-schemes project (#1045)db4dfc9Ref: cleaning CI and removing travis (#1041)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard: