Bump sentry-expo from 2.1.2 to 4.2.0

[dependabot[bot]]

Bumps sentry-expo from 2.1.2 to 4.2.0.

Changelog

Sourced from sentry-expo's changelog.

Changelog

4.0.5 — 2021-11-23

• Fixed using deviceYearClass from expo-constants, which is now deprecated. deviceYearClass is now pulled from expo-device

4.0.4 — 2021-10-25

• Fixed writing undefined in sentry.properties if using env variables instead of app.json

4.0.3 — 2021-09-28

• Fixed monorepo support for iOS
• Added --force-foreground flag to Sentry CLI commands during iOS builds due to an issue with Sentry: getsentry/sentry-react-native#1424

4.0.2 — 2021-09-27

• Upgrade @sentry/browser, @sentry/integrations, @sentry/react-native, @sentry/types to support Sentry React Native V3
• Fixed monorepo support for Android

4.0.1 — 2021-07-02

🐛 Bug fixes

• Do not force @sentry/browser and @sentry/integrations to v6.7.2.

4.0.0 — 2021-06-23

🛠 Breaking changes

• Removed expo-application, expo-constants, expo-device, and expo-updates as dependencies. From now on, developers will have to install these packages separately. This avoids a common issue where projects would end up having multiple versions of these libraries installed, but only one linked natively.

🐛 Bug fixes

• Only log "enableInExpoDevelopment" warning if enableInExpoDevelopment is not defined.

3.1.4 — 2021-04-23

🐛 Bug fixes

• No longer tracking Constants.installationId by default. Instead, tracking Constants.sessionId.
• Upgrades expo- dependencies. The new versions have dropped support for iOS 10; if you are bare workflow and haven't already dropped support for iOS 10, you have two options:
  1. Changing platform :ios, '10.0' to platform :ios, '11.0' in your Podfile
  2. Use the resolutions key in your package.json file to pin the versions of expo-application, expo-device, and expo-constants to their previous major versions.

3.1.3 — 2021-03-06

🐛 Bug fixes

• Fixed compilation errors on web

... (truncated)

Commits

• See full diff in compare view

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Looks like sentry-expo is no longer a dependency, so this is no longer needed.