deps: bump io.sentry:sentry-bom from 8.43.2 to 8.44.0

[dependabot]

Bumps io.sentry:sentry-bom from 8.43.2 to 8.44.0.

Release notes

Sourced from io.sentry:sentry-bom's releases.

8.44.0

Features

• Add enableStandaloneAppStartTracing option to send app start as a standalone transaction instead of attaching it as a child span of the first activity transaction (#5342)
  • Disabled by default; opt in via options.isEnableStandaloneAppStartTracing = true or manifest meta-data io.sentry.standalone-app-start-tracing.enable
  • Emits a transaction named App Start with op app.start, carrying the existing app start measurements and phase spans (process.load, contentprovider.load, application.load, activity lifecycle spans) as direct children of the root
  • The standalone transaction shares the same traceId as the first ui.load activity transaction so they remain linked in the trace view
  • Also covers non-activity starts (broadcast receivers, services, content providers)

Improvements

• Reduce boxing to improve performance (#5523, #5527, #5551)
• Replace Date with a unix timestamp in SentryNanotimeDate to improve performance (#5550)
  • SentryNanotimeDate is now marked @ApiStatus.Internal. A new (long unixDateMillis, long nanos) constructor was added, where unixDateMillis is milliseconds since the epoch. The existing (Date, long) constructor is retained but deprecated.

Dependencies

• Upgrade to asyncProfiler 4.4 (#5418)
• Bump Native SDK from v0.14.2 to v0.15.0 (#5528)
  • changelog
  • diff

Fixes

• Fix attachments being duplicated on native events that carry scope attachments (#5548)
• Fix performance collector scheduling many tasks in a row (#5524)

Changelog

Sourced from io.sentry:sentry-bom's changelog.

8.44.0

Features

• Add enableStandaloneAppStartTracing option to send app start as a standalone transaction instead of attaching it as a child span of the first activity transaction (#5342)
  • Disabled by default; opt in via options.isEnableStandaloneAppStartTracing = true or manifest meta-data io.sentry.standalone-app-start-tracing.enable
  • Emits a transaction named App Start with op app.start, carrying the existing app start measurements and phase spans (process.load, contentprovider.load, application.load, activity lifecycle spans) as direct children of the root
  • The standalone transaction shares the same traceId as the first ui.load activity transaction so they remain linked in the trace view
  • Also covers non-activity starts (broadcast receivers, services, content providers)

Improvements

• Reduce boxing to improve performance (#5523, #5527, #5551)
• Replace Date with a unix timestamp in SentryNanotimeDate to improve performance (#5550)
  • SentryNanotimeDate is now marked @ApiStatus.Internal. A new (long unixDateMillis, long nanos) constructor was added, where unixDateMillis is milliseconds since the epoch. The existing (Date, long) constructor is retained but deprecated.

Dependencies

• Upgrade to asyncProfiler 4.4 (#5418)
• Bump Native SDK from v0.14.2 to v0.15.0 (#5528)
  • changelog
  • diff

Fixes

• Fix attachments being duplicated on native events that carry scope attachments (#5548)
• Fix performance collector scheduling many tasks in a row (#5524)

Commits

• f944a75 release: 8.44.0
• 3a7603a perf(android): Replace Date with unix timestamp in SentryNanotimeDate (JAVA-5...
• 06b0d80 chore(android-sqlite): Repair start times of spans generated by SentrySQLiteD...
• ba01011 perf: Avoid boxing in doubleToBigDecimal timestamp serialization (#5551)
• e52b4e4 chore(deps): bump actions/setup-java in the github-actions group (#5554)
• 6dff1c9 chore: update scripts/update-sentry-native-ndk.sh to 0.15.0 (#5528)
• f36e6e3 fix(android): Stop duplicating attachments on native events (JAVA-559) (#5548)
• 773a0df ci: Remove Codecov and code coverage tooling (JAVA-560) (#5547)
• 3eb7173 feat(android-sqlite): Add SentrySQLiteDriver (JAVA-275) (#5466)
• 9d2f4e3 chore(samples-android): Support mavenLocal for builds that apply the SAGP (#5...
• 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 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)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.