Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 12, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Type Update Change Age Confidence
gradle (source) minor 8.10.2 -> 8.14.3 age confidence
gradle final minor 8.10.2-jdk17 -> 8.14.3-jdk17 age confidence
tomcat final patch 9.0.108-jdk17-temurin-jammy -> 9.0.109-jdk17-temurin-jammy age confidence
org.apache.xmlgraphics:batik-svg-dom dependencies minor 1.17 -> 1.19 age confidence
org.apache.xmlgraphics:batik-codec dependencies minor 1.17 -> 1.19 age confidence
org.apache.groovy:groovy-all (source) dependencies patch 4.0.26 -> 4.0.28 age confidence
net.logstash.logback:logstash-logback-encoder dependencies minor 8.0 -> 8.1 age confidence
io.sentry:sentry-logback dependencies minor 8.1.0 -> 8.21.1 age confidence
com.amazonaws:aws-java-sdk-s3 (source) dependencies patch 1.12.780 -> 1.12.791 age confidence
org.yaml:snakeyaml dependencies minor 2.3 -> 2.5 age confidence
ch.qos.logback:logback-access (source, changelog) dependencies patch 1.5.16 -> 1.5.18 age confidence
ch.qos.logback:logback-classic (source, changelog) dependencies patch 1.5.16 -> 1.5.18 age confidence
org.slf4j:jul-to-slf4j (source, changelog) dependencies patch 2.0.16 -> 2.0.17 age confidence
org.slf4j:jcl-over-slf4j (source, changelog) dependencies patch 2.0.16 -> 2.0.17 age confidence
org.slf4j:slf4j-api (source, changelog) dependencies patch 2.0.16 -> 2.0.17 age confidence
net.sf.jasperreports:jasperreports-pdf (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
net.sf.jasperreports:jasperreports-jdt (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
net.sf.jasperreports:jasperreports-json (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
net.sf.jasperreports:jasperreports-functions (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
net.sf.jasperreports:jasperreports-fonts (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
net.sf.jasperreports:jasperreports-excel-poi (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
net.sf.jasperreports:jasperreports (source) dependencies patch 7.0.2 -> 7.0.3 age confidence
io.dropwizard.metrics:metrics-logback (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
io.dropwizard.metrics:metrics-jmx (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
io.dropwizard.metrics:metrics-jvm (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
io.dropwizard.metrics:metrics-servlets (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
io.dropwizard.metrics:metrics-httpclient (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
io.dropwizard.metrics:metrics-servlet (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
io.dropwizard.metrics:metrics-core (source) dependencies patch 4.2.30 -> 4.2.37 age confidence
com.mchange:c3p0 (source) dependencies minor 0.10.2 -> 0.11.2 age confidence
org.postgresql:postgresql (source) dependencies patch 42.7.5 -> 42.7.7 age confidence
org.mockito:mockito-core dependencies minor 5.11.0 -> 5.19.0 age confidence
spotbugs (source) dependencies patch 4.9.4 -> 4.9.6 age confidence
commons-io:commons-io (source) dependencies minor 2.17.0 -> 2.20.0 age confidence
com.google.guava:guava dependencies minor 33.3.1-jre -> 33.5.0-jre age confidence
org.apache.groovy:groovy-json (source) dependencies patch 4.0.26 -> 4.0.28 age confidence
org.apache.groovy:groovy-xml (source) dependencies patch 4.0.26 -> 4.0.28 age confidence

Release Notes

gradle/gradle (gradle)

v8.14.3: 8.14.3

Compare Source

The Gradle team is excited to announce Gradle 8.14.3.

This is a patch release for 8.14. We recommend using 8.14.3 instead of 8.14.

Here are the highlights of this release:

  • Java 24 support
  • GraalVM Native Image toolchain selection
  • Enhancements to test reporting
  • Build Authoring improvements

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.3 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.3 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.2

Compare Source

v8.14.1: 8.14.1

Compare Source

The Gradle team is excited to announce Gradle 8.14.1.

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.1 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14

Compare Source

v8.13

Compare Source

v8.12.1: 8.12.1

Compare Source

The Gradle team is excited to announce Gradle 8.12.1.

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Abhiraj Adhikary,
Ayush Saxena,
Björn Kautler,
davidburstrom,
Dominic Fellbaum,
Emmanuel Ferdman,
Finn Petersen,
Johnny Lim,
Mahdi Hosseinzadeh,
Martin Bonnin,
Paint_Ninja,
Petter Måhlén,
Philip Wedemann,
stegeto22,
Tanish,
TheGoesen,
Tim Nielens,
Trout Zhang,
Victor Merkulov

Upgrade instructions

Switch your build to use Gradle 8.12.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.12.1

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.12: 8.12

Compare Source

The Gradle team is excited to announce Gradle 8.12.

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Abhiraj Adhikary,
Ayush Saxena,
Björn Kautler,
davidburstrom,
Dominic Fellbaum,
Emmanuel Ferdman,
Finn Petersen,
Johnny Lim,
Mahdi Hosseinzadeh,
Martin Bonnin,
Paint_Ninja,
Petter Måhlén,
Philip Wedemann,
stegeto22,
Tanish,
TheGoesen,
Tim Nielens,
Trout Zhang,
Victor Merkulov

Upgrade instructions

Switch your build to use Gradle 8.12 by updating your wrapper:

./gradlew wrapper --gradle-version=8.12

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.11.1: 8.11.1

Compare Source

This is a patch release for Gradle 8.11. We recommend users upgrade to 8.11.1 instead of 8.11.

It fixes the following issues:

  • #​31268 BuildEventsListenerRegistry corrupted with Isolated Projects and parallel configuration
  • #​31282 Running executables sporadically fails with ETXTBSY (Text file busy)
  • #​31284 ArrayIndexOutOfBoundsException after upgrading to gradle 8.11 when generating problems report
  • #​31310 Unable to run Gradle task in 8.10 due to bytecode interception

Read the Release Notes

Upgrade instructions

Switch your build to use Gradle 8.11.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.11.1

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.11: 8.11

Compare Source

The Gradle team is excited to announce Gradle 8.11.

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
alyssoncs,
Bilel MEDIMEGH,
Björn Kautler,
Chuck Thomas,
Daniel Lacasse,
Finn Petersen,
JK,
Jérémie Bresson,
luozexuan,
Mahdi Hosseinzadeh,
Markus Gaisbauer,
Matthew Haughton,
Matthew Von-Maszewski,
ploober,
Siarhei,
Titus James,
vrp0211

Upgrade instructions

Switch your build to use Gradle 8.11 by updating your wrapper:

./gradlew wrapper --gradle-version=8.11

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

getsentry/sentry-java (io.sentry:sentry-logback)

v8.21.1

Compare Source

Fixes
  • Use Kotlin stdlib 1.9.24 dependency instead of 2.2.0 for all Android modules (#​4707)
    • This fixes compile time issues if your app is using Kotlin < 2.x

v8.21.0

Compare Source

Fixes
  • Only set log template for logging integrations if formatted message differs from template (#​4682)
Features
  • Add support for Spring Boot 4 and Spring 7 (#​4601)
    • NOTE: Our sentry-opentelemetry-agentless-spring is not working yet for Spring Boot 4. Please use sentry-opentelemetry-agent until OpenTelemetry has support for Spring Boot 4.
  • Replace UUIDGenerator implementation with Apache licensed code (#​4662)
  • Replace Random implementation with MIT licensed code (#​4664)
  • Add support for vars attribute in SentryStackFrame (#​4686)
    • Breaking change: The type of the vars attribute has been changed from Map<String, String> to Map<String, Object>.

v8.20.0

Compare Source

Fixes
  • Do not use named capturing groups for regular expressions (#​4652)
    • This fixes a crash on Android versions below 8.0 (API level 26)
Features
  • Add onDiscard to enable users to track the type and amount of data discarded before reaching Sentry (#​4612)
    • Stub for setting the callback on Sentry.init:
      Sentry.init(options -> {
        ...
        options.setOnDiscard(
         (reason, category, number) -> {
           // Your logic to process discarded data
         });
      });

v8.19.1

Compare Source

[!Warning]
Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.

Fixes
  • Do not store No-Op scopes onto OpenTelemetry Context when wrapping (#​4631)
    • In 8.18.0 and 8.19.0 the SDK could break when initialized too late.

v8.19.0

Compare Source

[!Warning]
Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.

Features
  • Add a isEnableSystemEventBreadcrumbsExtras option to disable reporting system events extras for breadcrumbs (#​4625)
Improvements
  • Session Replay: Use main thread looper to schedule replay capture (#​4542)
  • Use single LifecycleObserver and multi-cast it to the integrations interested in lifecycle states (#​4567)
  • Add sentry.origin attribute to logs (#​4618)
    • This helps identify which integration captured a log event
  • Prewarm SentryExecutorService for better performance at runtime (#​4606)
Fixes
  • Cache network capabilities and status to reduce IPC calls (#​4560)
  • Deduplicate battery breadcrumbs (#​4561)
  • Remove unused method in ManifestMetadataReader (#​4585)
  • Have single NetworkCallback registered at a time to reduce IPC calls (#​4562)
  • Do not register for SystemEvents and NetworkCallbacks immediately when launched with non-foreground importance (#​4579)
  • Limit ProGuard keep rules for native methods within sentry-android-ndk to the io.sentry.** namespace. (#​4427)
    • If you relied on the Sentry SDK to keep native method names for JNI compatibility within your namespace, please review your ProGuard rules and ensure the configuration still works. Especially when you're not consuming any of the default Android proguard rules (proguard-android.txt or proguard-android-optimize.txt) the following config should be present:
    -keepclasseswithmembernames class * {
      native <methods>;
    }
    
  • Fix abstract method error in SentrySupportSQLiteDatabase (#​4597)
  • Ensure frame metrics listeners are registered/unregistered on the main thread (#​4582)
  • Do not report cached events as lost (#​4575)
    • Previously events were recorded as lost early despite being retried later through the cache
  • Move and flush unfinished previous session on init (#​4624)
    • This removes the need for unnecessary blocking our background queue for 15 seconds in the case of a background app start
  • Switch to compileOnly dependency for compose-ui-material (#​4630)
    • This fixes StackOverflowError when using OSS Licenses plugin
Dependencies

v8.18.0

Compare Source

Features
  • Add SentryUserFeedbackButton Composable (#​4559)
    • Also added Sentry.showUserFeedbackDialog static method
  • Add deadlineTimeout option (#​4555)
  • Add Ktor client integration (#​4527)
    • To use the integration, add a dependency on io.sentry:sentry-ktor-client, then install the SentryKtorClientPlugin on your HttpClient,
      e.g.:
      val client =
        HttpClient(Java) {
          install(io.sentry.ktorClient.SentryKtorClientPlugin) {
            captureFailedRequests = true
            failedRequestTargets = listOf(".*")
            failedRequestStatusCodes = listOf(HttpStatusCodeRange(500, 599))
          }
        }
Fixes
  • Allow multiple UncaughtExceptionHandlerIntegrations to be active at the same time (#​4462)
  • Prevent repeated scroll target determination during a single scroll gesture (#​4557)
    • This should reduce the number of ANRs seen in SentryGestureListener
  • Do not use Sentry logging API in JUL if logs are disabled (#​4574)
    • This was causing Sentry SDK to log warnings: "Sentry Log is disabled and this 'logger' call is a no-op."
  • Do not use Sentry logging API in Log4j2 if logs are disabled (#​4573)
    • This was causing Sentry SDK to log warnings: "Sentry Log is disabled and this 'logger' call is a no-op."
  • SDKs send queue is no longer shutdown immediately on re-init (#​4564)
    • This means we're no longer losing events that have been enqueued right before SDK re-init.
  • Reduce scope forking when using OpenTelemetry (#​4565)
    • Sentry.withScope now has the correct current scope passed to the callback. Previously our OpenTelemetry integration forked scopes an additional.
    • Overall the SDK is now forking scopes a bit less often.

v8.17.0

Compare Source

Features
  • Send Timber logs through Sentry Logs (#​4490)
    • Enable the Logs feature in your SentryOptions or with the io.sentry.logs.enabled manifest option and the SDK will automatically send Timber logs to Sentry, if the TimberIntegration is enabled.
    • The SDK will automatically detect Timber and use it to send logs to Sentry.
  • Send logcat through Sentry Logs (#​4487)
    • Enable the Logs feature in your SentryOptions or with the io.sentry.logs.enabled manifest option and the SDK will automatically send logcat logs to Sentry, if the Sentry Android Gradle plugin is applied.
    • To set the logcat level check the Logcat integration documentation.
  • Read build tool info from sentry-debug-meta.properties and attach it to events (#​4314)
Dependencies
  • Bump OpenTelemetry (#​4532)
    • opentelemetry-sdk to 1.51.0
    • opentelemetry-instrumentation to 2.17.0
    • opentelemetry-javaagent to 2.17.0
    • opentelemetry-semconv to 1.34.0
    • We are now configuring OpenTelemetry to still behave the same way it did before for span names it generates in GraphQL auto instrumentation (#​4537)
  • Bump Gradle from v8.14.2 to v8.14.3 (#​4540)
Fixes
  • Use Spring Boot Starter 3 in sentry-spring-boot-starter-jakarta (#​4545)
    • While refactoring our dependency management, we accidentally added Spring Boot 2 and Spring Boot Starter 2 as dependencies of sentry-spring-boot-starter-jakarta, which is intended for Spring Boot 3.
    • Now, the correct dependencies (Spring Boot 3 and Spring Boot Starter 3) are being added.

v8.16.0

Compare Source

Features
  • Send JUL logs to Sentry as logs (#​4518)
    • You need to enable the logs feature, either in sentry.properties:
      logs.enabled=true
    • Or, if you manually initialize Sentry, you may also enable logs on Sentry.init:
      Sentry.init(options -> {
        ...
        options.getLogs().setEnabled(true);
      });
    • It is also possible to set the minimumLevel in logging.properties, meaning any log message >= the configured level will be sent to Sentry and show up under Logs:
      io.sentry.jul.SentryHandler.minimumLevel=CONFIG
  • Send Log4j2 logs to Sentry as logs (#​4517)
    • You need to enable the logs feature either in sentry.properties:
      logs.enabled=true
    • If you manually initialize Sentry, you may also enable logs on Sentry.init:
      Sentry.init(options -> {
        ...
        options.getLogs().setEnabled(true);
      });
    • It is also possible to set the minimumLevel in log4j2.xml, meaning any log message >= the configured level will be sent to Sentry and show up under Logs:
      <Sentry name="Sentry"
          dsn="your DSN"
          minimumBreadcrumbLevel="DEBUG"
          minimumEventLevel="WARN"
          minimumLevel="DEBUG"
      />

v8.15.1

Compare Source

Fixes
  • Enabling Sentry Logs through Logback in Spring Boot config did not work in 3.15.0 (#​4523)

v8.15.0

Compare Source

Features
  • Add chipset to device context (#​4512)
Fixes
  • No longer send out empty log envelopes (#​4497)
  • Session Replay: Expand fix for crash on devices to all Unisoc/Spreadtrum chipsets (#​4510)
  • Log parameter objects are now turned into String via toString (#​4515)
    • One of the two SentryLogEventAttributeValue constructors did not convert the value previously.
  • Logs are now flushed on shutdown (#​4503)
  • User Feedback: Do not redefine system attributes for SentryUserFeedbackButton, but reference them instead (#​4519)
Features
  • Send Logback logs to Sentry as logs (#​4502)
    • You need to enable the logs feature and can also set the minimumLevel for log events:
      <appender name="sentry" class="io.sentry.logback.SentryAppender">
        <options>
          <!-- NOTE: Replace the test DSN below with YOUR OWN DSN to see the events from this app in your Sentry project/dashboard -->
          <dsn>https://502f25099c204a2fbf4cb16edc5975d1@&#8203;o447951.ingest.sentry.io/5428563</dsn>
          <logs>
            <enabled>true</enabled>
          </logs>
        </options>
        <!-- Demonstrates how to modify the minimum values -->
        <!-- Default for Events is ERROR -->
        <minimumEventLevel>WARN</minimumEventLevel>
        <!-- Default for Breadcrumbs is INFO -->
        <minimumBreadcrumbLevel>DEBUG</minimumBreadcrumbLevel>
        <!-- Default for Log Events is INFO -->
        <minimumLevel>INFO</minimumLevel>
      </appender>
    • For Spring Boot you may also enable it in application.properties / application.yml:
      sentry.logs.enabled=true
      sentry.logging.minimum-level=error
    • If you manually initialize Sentry, you may also enable logs on Sentry.init:
      Sentry.init(options -> {
        ...
        options.getLogs().setEnabled(true);
      });
    • Enabling via sentry.properties is also possible:
      logs.enabled=true
  • Automatically use SentryOptions.Logs.BeforeSendLogCallback Spring beans (#​4509)
Dependencies

v8.14.0

Compare Source

Fixes
  • Fix Session Replay masking for newer versions of Jetpack Compose (1.8+) (#​4485)
Features
  • Add New User Feedback Widget (#​4450)
    • This widget is a custom button that can be used to show the user feedback form
  • Add New User Feedback form (#​4384)
    • We now introduce SentryUserFeedbackDialog, which extends AlertDialog, inheriting the show() and cancel() methods, among others.
      To use it, just instantiate it and call show() on the instance (Sentry must be previously initialized).
      For customization options, please check the User Feedback documentation.
      import io.sentry.android.core.SentryUserFeedbackDialog;
      
      new SentryUserFeedbackDialog.Builder(context).create().show();
      import io.sentry.android.core.SentryUserFeedbackDialog
      
      SentryUserFeedbackDialog.Builder(context).create().show()
  • Add user.id, user.name and user.email to log attributes (#​4486)
  • User name attribute has been deprecated, please use username instead (#​4486)
  • Add device (device.brand, device.model and device.family) and OS (os.name and os.version) attributes to logs (#​4493)
  • Serialize preContext and postContext in SentryStackFrame (#​4482)
Internal
  • User Feedback now uses SentryUser.username instead of SentryUser.name (#​4494)

v8.13.3

Compare Source

Fixes
  • Send UI Profiling app start chunk when it finishes (#​4423)
  • Republish Javadoc #​4457
  • Finalize OkHttpEvent even if no active span in SentryOkHttpInterceptor #​4469
  • Session Replay: Do not capture current replay for cached events from the past (#​4474)
  • Session Replay: Correctly capture Dialogs and non full-sized windows (#​4354)
  • Session Replay: Fix inconsistent segment_id (#​4471)
  • Session Replay: Fix crash on devices with the Unisoc/Spreadtrum T606 chipset (#​4477)

v8.13.2

Compare Source

Fixes
  • Don't apply Spring Boot plugin in sentry-spring-boot-jakarta (#​4456)
    • The jar for io.sentry:sentry-spring-boot-jakarta is now correctly being built and published to Maven Central.

v8.13.1

Compare Source

Fixes
  • Fix SentryAndroid.init crash if SDK is initialized from a background thread while an Activity is in resumed state (#​4449)
Dependencies

v8.13.0

Compare Source

Features
  • Add debug mode for Session Replay masking (#​4357)
    • Use Sentry.replay().enableDebugMaskingOverlay() to overlay the screen with the Session Replay masks.
    • The masks will be invalidated at most once per frameRate (default 1 fps).
  • Extend Logs API to allow passing in attributes (#​4402)
    • Sentry.logger.log now takes a SentryLogParameters
    • Use SentryLogParameters.create(SentryAttributes.of(...)) to pass attributes
      • Attribute values may be of type string, boolean, integer or double.
      • Other types will be converted to string. Currently we simply call toString() but we might offer more in the future.
      • You may manually flatten complex types into multiple separate attributes of simple types.
        • e.g. intead of SentryAttribute.named("point", Point(10, 20)) you may store it as SentryAttribute.integerAttribute("point.x", point.x) and SentryAttribute.integerAttribute("point.y", point.y)
      • SentryAttribute.named() will automatically infer the type or fall back to string.
      • SentryAttribute.booleanAttribute() takes a Boolean value
      • SentryAttribute.integerAttribute() takes a Integer value
      • SentryAttribute.doubleAttribute() takes a Double value
      • SentryAttribute.stringAttribute() takes a String value
    • We opted for handling parameters via SentryLogParameters to avoid creating tons of overloads that are ambiguous.
Fixes
  • Isolation scope is now forked in OtelSentrySpanProcessor instead of OtelSentryPropagator (#​4434)
    • Since propagator may never be invoked we moved the location where isolation scope is forked.
    • Not invoking OtelSentryPropagator.extract or having a sentry-trace header that failed to parse would cause isolation scope not to be forked.
    • This in turn caused data to bleed between scopes, e.g. from one request into another
Dependencies

Configuration

📅 Schedule: Branch creation - "after 5pm on the first day of the month,on the first day of the month" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot added the dependencies Update the dependencies label Sep 12, 2025
@renovate renovate bot enabled auto-merge (squash) September 12, 2025 18:14
@renovate renovate bot force-pushed the renovate/master-all-patchminor-versions branch 2 times, most recently from 03814e9 to 62d2d39 Compare September 16, 2025 05:12
@renovate renovate bot force-pushed the renovate/master-all-patchminor-versions branch from 62d2d39 to 2785bb2 Compare September 17, 2025 22:44
@renovate
Copy link
Contributor Author

renovate bot commented Sep 18, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot merged commit a413e46 into master Sep 18, 2025
15 checks passed
@renovate renovate bot deleted the renovate/master-all-patchminor-versions branch September 18, 2025 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Update the dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants