Bump io.sentry.android.gradle from 3.14.0 to 4.1.0

[dependabot]

Bumps io.sentry.android.gradle from 3.14.0 to 4.1.0.

Release notes

Sourced from io.sentry.android.gradle's releases.

4.1.0

Features

• Do not consider user-defined sentry versions when auto-installing integrations. This is necessary because we want to align integrations versions to the same one as one of sentry-android-core/sentry/sentry-android/sentry-spring-boot to prevent runtime crashes due to binary incompatibility. (#602)
  • If you have directly defined one of the core versions, we will use that to install integrations, otherwise autoInstallation.sentryVersion or the default bundled SDK version is used.

This means if you have defined something like that:

// direct deps
dependencies {
  implementation("io.sentry:sentry-android-core:7.0.0")
  implementation("io.sentry:sentry-android-okhttp:6.34.0")
}
// or with the gradle plugin
sentry {
autoInstallation.sentryVersion = '7.0.0' // or the latest version bundled within the plugin
}
dependencies {
implementation("io.sentry:sentry-android-okhttp:6.34.0")
}

Then in both cases it will use 7.0.0 when installing the sentry-android-okhttp integration and print a warning that we have overridden the version.

• Add aarch64 sentry-cli (#611)

  • This is used when the build is executed inside a docker container on an Apple silicon chip (e.g. M1)

• Instrument ContentProvider/Application onCreate calls to measure app-start performance (#565)

  • This feature requires the sentry-java SDK version 7.1.0 and is enabled by default
  • To disable the feature, set sentry.tracingInstrumentation.appStart.enabled to false

sentry {
  tracingInstrumentation {
    appStart {
      enabled.set(false)
    }
  }
}

Fixes

• Fix sentry-cli url parameter position (#610)

Dependencies

• Bump CLI from v2.22.3 to v2.23.0 (#607)
  • changelog

... (truncated)

Changelog

Sourced from io.sentry.android.gradle's changelog.

4.1.0

Features

• Do not consider user-defined sentry versions when auto-installing integrations. This is necessary because we want to align integrations versions to the same one as one of sentry-android-core/sentry/sentry-android/sentry-spring-boot to prevent runtime crashes due to binary incompatibility. (#602)
  • If you have directly defined one of the core versions, we will use that to install integrations, otherwise autoInstallation.sentryVersion or the default bundled SDK version is used.

This means if you have defined something like that:

// direct deps
dependencies {
  implementation("io.sentry:sentry-android-core:7.0.0")
  implementation("io.sentry:sentry-android-okhttp:6.34.0")
}
// or with the gradle plugin
sentry {
autoInstallation.sentryVersion = '7.0.0' // or the latest version bundled within the plugin
}
dependencies {
implementation("io.sentry:sentry-android-okhttp:6.34.0")
}

Then in both cases it will use 7.0.0 when installing the sentry-android-okhttp integration and print a warning that we have overridden the version.

• Add aarch64 sentry-cli (#611)

  • This is used when the build is executed inside a docker container on an Apple silicon chip (e.g. M1)

• Instrument ContentProvider/Application onCreate calls to measure app-start performance (#565)

  • This feature requires the sentry-java SDK version 7.1.0 and is enabled by default
  • To disable the feature, set sentry.tracingInstrumentation.appStart.enabled to false

sentry {
  tracingInstrumentation {
    appStart {
      enabled.set(false)
    }
  }
}

Fixes

• Fix sentry-cli url parameter position (#610)

Dependencies

• Bump CLI from v2.22.3 to v2.23.0 (#607)

... (truncated)

Commits

• cd9afc6 release: 4.1.0
• c1eba4d Instrument ContentProvider/Application onCreate calls to measure app-start pe...
• b087e82 chore(deps): update Android SDK to v7.1.0 (#612)
• bfa12c3 Add aarch64 sentry-cli (#611)
• 123e7ac Fix url parameter position (#610)
• f6fc72f chore(deps): update CLI to v2.23.0 (#607)
• 994a5de Do not consider user-defined sentry integration versions when auto-installing...
• ef3940b Merge branch 'release/4.0.0'
• 188e7e2 release: 4.0.0
• 240504b Changelog and v7 bump (#604)
• Additional commits viewable 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[akshaaatt]

@dependabot rebase

[dependabot]

Superseded by #313.