search

SAP / olingo-jpa-processor-v4

The JPA Processor fills the gap between Olingo V4 and the database, by providing a mapping between JPA metadata and OData metadata, generating queries and supporting the entity manipulations.
Apache License 2.0
122 stars 78 forks source link

Bump com.sap.hcp.cf.logging:cf-java-logging-support-log4j2 from 3.8.0 to 3.8.3 in /jpa #291

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

Bumps com.sap.hcp.cf.logging:cf-java-logging-support-log4j2 from 3.8.0 to 3.8.3.

Release notes

Sourced from com.sap.hcp.cf.logging:cf-java-logging-support-log4j2's releases.

v3.8.3

This is a bugfix release for the dynatrace exporter for metrics. Dynatrace requires metrics of kind sum to have delta aggregation temporality. Metrics with cumulative aggregation temporality are currently dropped by the API.

What's Changed

Full Changelog: https://github.com/SAP/cf-java-logging-support/compare/v3.8.2...v3.8.3

v3.8.2

This release just improves on the cf-java-logging-support-opentelemetry-agent-extension. It now provides a dynatrace exporters for metrics. This will detect bindings to SAP BTP APM and allow the OpenTelemetry Java Agent to forward metrics to Dynatrace. See the documentation on the required configuration.

What's Changed

Full Changelog: https://github.com/SAP/cf-java-logging-support/compare/v3.8.1...v3.8.2

v3.8.1

This release upgrades Logback to version 1.2.13 to mitigate CVE-2023-6378. Please upgrade your dependencies. Note, that the CVE issue is within an optionally configurable log receiver of an application, that not only requires explicit configuration in the logback files, but also adding an appropriate route in the CF manifest of the application.

The release also extends the module: cf-java-logging-support-opentelemetry-agent-extension. It now provides an cloud-logging exporter to be used with the OpenTelemetry Java Agent. This allows to combine the SAP Cloud Logging support with other OpenTelemetry targets. Additionally, all bound service instances will now be configured as data sinks.

What's Changed

Full Changelog: https://github.com/SAP/cf-java-logging-support/compare/v3.8.0...v3.8.1

Commits


Dependabot compatibility score

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 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[bot] commented 5 months ago

Looks like com.sap.hcp.cf.logging:cf-java-logging-support-log4j2 is up-to-date now, so this is no longer needed.