fix(deps): update all non-major application-server dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.sentry:sentry-spring-boot-starter-jakarta	8.5.0 -> 8.7.0
org.flywaydb:flyway-database-postgresql (source)	11.5.0 -> 11.7.0
org.flywaydb:flyway-core (source)	11.5.0 -> 11.7.0
org.flywaydb.flyway	11.4.0 -> 11.7.0

---

Release Notes

getsentry/sentry-java (io.sentry:sentry-spring-boot-starter-jakarta)

v8.7.0

Compare Source

Features

• UI Profiling GA

  Continuous Profiling is now GA, named UI Profiling. To enable it you can use one of the following options. More info can be found at https://docs.sentry.io/platforms/android/profiling/.
  Note: Both options.profilesSampler and options.profilesSampleRate must not be set to enable UI Profiling.
  To keep the same transaction-based behaviour, without the 30 seconds limitation, you can use the trace lifecycle mode.

  <application>
    <!-- Enable UI profiling, adjust in production env. This is evaluated only once per session -->
    <meta-data android:name="io.sentry.traces.profiling.session-sample-rate" android:value="1.0" />
    <!-- Set profiling lifecycle, can be `manual` (controlled through `Sentry.startProfiler()` and `Sentry.stopProfiler()`) or `trace` (automatically starts and stop a profile whenever a sampled trace starts and finishes) -->
    <meta-data android:name="io.sentry.traces.profiling.lifecycle" android:value="trace" />
    <!-- Enable profiling on app start. The app start profile will be stopped automatically when the app start root span finishes -->
    <meta-data android:name="io.sentry.traces.profiling.start-on-app-start" android:value="true" />
  </application>

  import io.sentry.ProfileLifecycle;
  import io.sentry.android.core.SentryAndroid;
  
  SentryAndroid.init(context, options -> {
      // Enable UI profiling, adjust in production env. This is evaluated only once per session
      options.setProfileSessionSampleRate(1.0);
      // Set profiling lifecycle, can be `manual` (controlled through `Sentry.startProfiler()` and `Sentry.stopProfiler()`) or `trace` (automatically starts and stop a profile whenever a sampled trace starts and finishes)
      options.setProfileLifecycle(ProfileLifecycle.TRACE);
      // Enable profiling on app start. The app start profile will be stopped automatically when the app start root span finishes
      options.setStartProfilerOnAppStart(true);
    });

  import io.sentry.ProfileLifecycle
  import io.sentry.android.core.SentryAndroid
  
  SentryAndroid.init(context, { options ->
    // Enable UI profiling, adjust in production env. This is evaluated only once per session
    options.profileSessionSampleRate = 1.0
    // Set profiling lifecycle, can be `manual` (controlled through `Sentry.startProfiler()` and `Sentry.stopProfiler()`) or `trace` (automatically starts and stop a profile whenever a sampled trace starts and finishes)
    options.profileLifecycle = ProfileLifecycle.TRACE
    // Enable profiling on app start. The app start profile will be stopped automatically when the app start root span finishes
    options.isStartProfilerOnAppStart = true
    })

  • Continuous Profiling - Stop when app goes in background (#​4311)
  • Continuous Profiling - Add delayed stop (#​4293)
  • Continuous Profiling - Out of Experimental (#​4310)

Fixes

• Compress Screenshots on a background thread (#​4295)

v8.6.0

Compare Source

Behavioral Changes

• The Sentry SDK will now crash on startup if mixed versions have been detected (#​4277)
  • On Sentry.init / SentryAndroid.init the SDK now checks if all Sentry Java / Android SDK dependencies have the same version.
  • While this may seem like a bad idea at first glance, mixing versions of dependencies has a very high chance of causing a crash later. We opted for a controlled crash that's hard to miss.
  • Note: This detection only works for new versions of the SDK, so please take this as a reminder to check your SDK version alignment manually when upgrading the SDK to this version and then you should be good.
  • The SDK will also print log messages if mixed versions have been detected at a later point. (#​4270)
    • This takes care of cases missed by the startup check above due to older versions.

Features

• Increase http timeouts from 5s to 30s to have a better chance of events being delivered without retry (#​4276)
• Add MANIFEST.MF to Sentry JARs (#​4272)
• Retain baggage sample rate/rand values as doubles (#​4279)
• Introduce fatal SDK logger (#​4288)
  • We use this to print out messages when there is a problem that prevents the SDK from working correctly.
  • One example for this is when the SDK has been configured with mixed dependency versions where we print out details, which module and version are affected.

Fixes

• Do not override user-defined SentryOptions (#​4262)
• Session Replay: Change bitmap config to ARGB_8888 for screenshots (#​4282)
• The MANIFEST.MF of sentry-opentelemetry-agent now has Implementation-Version set to the raw version (#​4291)
  • An example value would be 8.6.0
  • The value of the Sentry-Version-Name attribute looks like sentry-8.5.0-otel-2.10.0
• Fix tags missing for compose view hierarchies (#​4275)
• Do not leak SentryFileInputStream/SentryFileOutputStream descriptors and channels (#​4296)
• Remove "not yet implemented" from Sentry.flush comment (#​4305)

Internal

• Added platform to SentryEnvelopeItemHeader (#​4287)
  • Set android platform to ProfileChunk envelope item header

Dependencies

• Bump Native SDK from v0.8.1 to v0.8.3 (#​4267, #​4298)
  • changelog
  • diff
• Bump Spring Boot from 2.7.5 to 2.7.18 (#​3496)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (0746c2e)	6499	877	13.49%
Head commit (07e9578)	6499 (+0)	877 (+0)	13.49% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#613)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences