Bump the prod-avhengigheter group across 1 directory with 6 updates

[dependabot]

Bumps the prod-avhengigheter group with 6 updates in the / directory:

Package	From	To
no.nav.familie.felles:felles	3.20250311182943_dac8027	3.20250312114810_5371990
io.sentry:sentry-bom	8.3.0	8.4.0
io.getunleash:unleash-client-java	10.1.1	10.2.0
no.nav.familie:prosessering-core	2.20250311132904_6ee7728	2.20250317081900_f756677
no.nav.familie.kontrakter:felles	3.0_20250313112514_5a97829	3.0_20250317084213_0b7e8b1
no.nav.familie.kontrakter:barnetrygd	3.0_20250313112514_5a97829	3.0_20250317084213_0b7e8b1

Updates no.nav.familie.felles:felles from 3.20250311182943_dac8027 to 3.20250312114810_5371990

Commits

• See full diff in compare view

Updates io.sentry:sentry-bom from 8.3.0 to 8.4.0

Release notes

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

8.4.0

Fixes

• The SDK now handles null on many APIs instead of expecting a non null value (#4245)
  • Certain APIs like setTag, setData, setExtra, setContext previously caused a NullPointerException when invoked with either null key or value.
  • The SDK now tries to have a sane fallback when null is passed and no longer throws NullPointerException
  • If null is passed, the SDK will
    • do nothing if a null key is passed, returning null for non void methods
    • remove any previous value if the new value is set to null
• Add support for setting in-app-includes/in-app-excludes via AndroidManifest.xml (#4240)
• Modifications to OkHttp requests are now properly propagated to the affected span / breadcrumbs (#4238)
  • Please ensure the SentryOkHttpInterceptor is added last to your OkHttpClient, as otherwise changes to the Request by subsequent interceptors won't be considered
• Fix "class ch.qos.logback.classic.spi.ThrowableProxyVO cannot be cast to class ch.qos.logback.classic.spi.ThrowableProxy" (#4206)
  • In this case we cannot report the Throwable to Sentry as it's not available
  • If you are using OpenTelemetry v1 OpenTelemetryAppender, please consider upgrading to v2
• Pass OpenTelemetry span attributes into TracesSampler callback (#4253)
  • SamplingContext now has a getAttribute method that grants access to OpenTelemetry span attributes via their String key (e.g. http.request.method)
• Fix AbstractMethodError when using SentryTraced for Jetpack Compose (#4255)
• Assume http.client for span op if not a root span (#4257)
• Avoid unnecessary copies when using CopyOnWriteArrayList (#4247)
  • This affects in particular SentryTracer.getLatestActiveSpan which would have previously copied all child span references. This may have caused OutOfMemoryError on certain devices due to high frequency of calling the method.

Features

• The SDK now automatically propagates the trace-context to the native layer. This allows to connect errors on different layers of the application. (#4137)
• Capture OpenTelemetry span events (#3564)
  • OpenTelemetry spans may have exceptions attached to them (openTelemetrySpan.recordException). We can now send those to Sentry as errors.
  • Set capture-open-telemetry-events=true in sentry.properties to enable it
  • Set sentry.capture-open-telemetry-events=true in Springs application.properties to enable it
  • Set sentry.captureOpenTelemetryEvents: true in Springs application.yml to enable it

Behavioural Changes

• Use java.net.URI for parsing URLs in UrlUtils (#4210)
  • This could affect grouping for issues with messages containing URLs that fall in known corner cases that were handled incorrectly previously (e.g. email in URL path)

Internal

• Also use port when checking if a request is made to Sentry DSN (#4231)
  • For our OpenTelemetry integration we check if a span is for a request to Sentry
  • We now also consider the port when performing this check

Dependencies

• Bump Native SDK from v0.7.20 to v0.8.1 (#4137)
  • changelog
  • diff

Changelog

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

8.4.0

Fixes

• The SDK now handles null on many APIs instead of expecting a non null value (#4245)
  • Certain APIs like setTag, setData, setExtra, setContext previously caused a NullPointerException when invoked with either null key or value.
  • The SDK now tries to have a sane fallback when null is passed and no longer throws NullPointerException
  • If null is passed, the SDK will
    • do nothing if a null key is passed, returning null for non void methods
    • remove any previous value if the new value is set to null
• Add support for setting in-app-includes/in-app-excludes via AndroidManifest.xml (#4240)
• Modifications to OkHttp requests are now properly propagated to the affected span / breadcrumbs (#4238)
  • Please ensure the SentryOkHttpInterceptor is added last to your OkHttpClient, as otherwise changes to the Request by subsequent interceptors won't be considered
• Fix "class ch.qos.logback.classic.spi.ThrowableProxyVO cannot be cast to class ch.qos.logback.classic.spi.ThrowableProxy" (#4206)
  • In this case we cannot report the Throwable to Sentry as it's not available
  • If you are using OpenTelemetry v1 OpenTelemetryAppender, please consider upgrading to v2
• Pass OpenTelemetry span attributes into TracesSampler callback (#4253)
  • SamplingContext now has a getAttribute method that grants access to OpenTelemetry span attributes via their String key (e.g. http.request.method)
• Fix AbstractMethodError when using SentryTraced for Jetpack Compose (#4255)
• Assume http.client for span op if not a root span (#4257)
• Avoid unnecessary copies when using CopyOnWriteArrayList (#4247)
  • This affects in particular SentryTracer.getLatestActiveSpan which would have previously copied all child span references. This may have caused OutOfMemoryError on certain devices due to high frequency of calling the method.

Features

• The SDK now automatically propagates the trace-context to the native layer. This allows to connect errors on different layers of the application. (#4137)
• Capture OpenTelemetry span events (#3564)
  • OpenTelemetry spans may have exceptions attached to them (openTelemetrySpan.recordException). We can now send those to Sentry as errors.
  • Set capture-open-telemetry-events=true in sentry.properties to enable it
  • Set sentry.capture-open-telemetry-events=true in Springs application.properties to enable it
  • Set sentry.captureOpenTelemetryEvents: true in Springs application.yml to enable it

Behavioural Changes

• Use java.net.URI for parsing URLs in UrlUtils (#4210)
  • This could affect grouping for issues with messages containing URLs that fall in known corner cases that were handled incorrectly previously (e.g. email in URL path)

Internal

• Also use port when checking if a request is made to Sentry DSN (#4231)
  • For our OpenTelemetry integration we check if a span is for a request to Sentry
  • We now also consider the port when performing this check

Dependencies

• Bump Native SDK from v0.7.20 to v0.8.1 (#4137)
  • changelog
  • diff

Commits

• be2d574 release: 8.4.0
• e5e6905 Assume http.client for span op if not a root span (#4257)
• 9fba6e3 Fix misuses of CopyOnWriteArrayList (#4247)
• 0b8cee0 Update CHANGELOG.md (#4248)
• 2882875 Fix AbstractMethodError when using SentryTraced for Jetpack Compose (#4255)
• 9683566 Pass OpenTelemetry span attributes into TracesSampler callback (#4253)
• 878fd7b Fix "class ch.qos.logback.classic.spi.ThrowableProxyVO cannot be cast to clas...
• 21a214b Avoid NPEs from SDK in API like setTag, setData, setContext (#4245)
• 5eb3279 Replace RestTemplate with OkHttp for system tests (#4239)
• ac9ebcd Add distributed tracing tests to more modules (#4237)
• Additional commits viewable in compare view

Updates io.getunleash:unleash-client-java from 10.1.1 to 10.2.0

Release notes

Sourced from io.getunleash:unleash-client-java's releases.

v10.2.0

What's Changed

• feat: add environmentEnabled property on feature defs by @​sighphyre in Unleash/unleash-client-java#295

Full Changelog: Unleash/unleash-client-java@v10.1.1...v10.2.0

Commits

• 5b85982 chore: remove tag from scm config
• 0b9b833 chore: prepare for next release
• 8608cd1 Releasing version 10.2.0
• d0327ba feat: add environmentEnabled property on feature defs (#295)
• See full diff in compare view

Updates no.nav.familie:prosessering-core from 2.20250311132904_6ee7728 to 2.20250317081900_f756677

Commits

• See full diff in compare view

Updates no.nav.familie.kontrakter:felles from 3.0_20250313112514_5a97829 to 3.0_20250317084213_0b7e8b1

Commits

• See full diff in compare view

Updates no.nav.familie.kontrakter:barnetrygd from 3.0_20250313112514_5a97829 to 3.0_20250317084213_0b7e8b1

Commits

• See full diff in compare view

Updates no.nav.familie.kontrakter:barnetrygd from 3.0_20250313112514_5a97829 to 3.0_20250317084213_0b7e8b1

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions