Skip to content

Bump the all-maven-dependencies group across 2 directories with 3 updates - #77

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/maven/all-maven-dependencies-8d2b922ec8
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/maven/all-maven-dependencies-8d2b922ec8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 10, 2026

Copy link
Copy Markdown
Contributor

Bumps the all-maven-dependencies group with 3 updates in the / directory: com.sap.cloud.security:java-bom, org.codehaus.mojo:flatten-maven-plugin and com.diffplug.spotless:spotless-maven-plugin.
Bumps the all-maven-dependencies group with 3 updates in the /srv directory: com.sap.cloud.security:java-bom, org.codehaus.mojo:flatten-maven-plugin and com.diffplug.spotless:spotless-maven-plugin.

Updates com.sap.cloud.security:java-bom from 4.3.0 to 4.3.1

Release notes

Sourced from com.sap.cloud.security:java-bom's releases.

4.3.1

  • Retry token, token-key, and OIDC-discovery requests on network errors (token-client, token-client-spring, token-client-spring-3)
    • The retry feature previously only acted on configured HTTP status codes. A network error (connection reset, read timeout, TLS handshake error) was rethrown immediately, so transient network failures during access-token, JWKS, or OIDC-discovery retrieval were never retried — even with retry enabled and maxRetryAttempts configured. In the plain client this surfaced as Error retrieving token keys: null during short identity-service blips.
    • Affected classes now retry on network errors as well, bounded by the existing maxRetryAttempts and retryDelayTime:
      • DefaultOAuth2TokenService, DefaultOAuth2TokenKeyService, DefaultOidcConfigurationService (retry on IOException)
      • XsuaaOAuth2TokenService, SpringOAuth2TokenKeyService, SpringOidcConfigurationService (retry on ResourceAccessException)
    • The Spring variants additionally route retryable HTTP status codes (HttpStatusCodeException) through the same retry handling, so the configured retryStatusCodes now take effect even though RestTemplate surfaces non-2xx responses as exceptions.
    • An already-decided HTTP outcome (OAuth2ServiceException) is still never retried.
    • This aligns the behavior with the documented retry feature, which states that requests failing due to "network issues, such as timeouts or connection errors" are retried.
Changelog

Sourced from com.sap.cloud.security:java-bom's changelog.

4.3.1

  • Retry token, token-key, and OIDC-discovery requests on network errors (token-client, token-client-spring, token-client-spring-3)
    • The retry feature previously only acted on configured HTTP status codes. A network error (connection reset, read timeout, TLS handshake error) was rethrown immediately, so transient network failures during access-token, JWKS, or OIDC-discovery retrieval were never retried — even with retry enabled and maxRetryAttempts configured. In the plain client this surfaced as Error retrieving token keys: null during short identity-service blips.
    • Affected classes now retry on network errors as well, bounded by the existing maxRetryAttempts and retryDelayTime:
      • DefaultOAuth2TokenService, DefaultOAuth2TokenKeyService, DefaultOidcConfigurationService (retry on IOException)
      • XsuaaOAuth2TokenService, SpringOAuth2TokenKeyService, SpringOidcConfigurationService (retry on ResourceAccessException)
    • The Spring variants additionally route retryable HTTP status codes (HttpStatusCodeException) through the same retry handling, so the configured retryStatusCodes now take effect even though RestTemplate surfaces non-2xx responses as exceptions.
    • An already-decided HTTP outcome (OAuth2ServiceException) is still never retried.
    • This aligns the behavior with the documented retry feature, which states that requests failing due to "network issues, such as timeouts or connection errors" are retried.
Commits
  • e2bf023 fix(token-client): retry on network errors across plain + Spring clients (4.3...
  • d4212cf update maven central deployment name (#2067)
  • See full diff in compare view

Updates org.codehaus.mojo:flatten-maven-plugin from 1.8.0 to 1.9.0

Release notes

Sourced from org.codehaus.mojo:flatten-maven-plugin's releases.

1.9.0

Flatten Maven Plugin 1.9.0 fixes CI-friendly property interpolation when custom pomElements are configured, updates its Plexus XML/interpolation dependencies, and cleans up declared Maven dependencies. It requires Maven 3.9.0 or later and Java 8 or later.

✨ Highlights

  • CI-friendly property interpolation with custom <pomElements>: Fixed a bug where configuring custom <pomElements> alongside <flattenMode>resolveCiFriendliesOnly</flattenMode> failed to initialize the CI-friendly property interpolator, leaving ${revision}, ${sha1}, and ${changelist} placeholders unresolved in the flattened POM (#528).
  • Updated Plexus stack: Upgraded plexus-xml to 3.1.0, plexus-utils to 4.1.0, and plexus-interpolation to 1.30.0 (#526, #527, #533).

🚨 Removed

🐛 Bug Fixes

📝 Documentation updates

👻 Maintenance

🔧 Build

📦 Dependency updates

  • Bump com.google.guava:guava from 32.0.0-jre to 33.7.2-jre in /src/it/projects/bom-pomElements/bom (#554, #559) @dependabot[bot]
  • Bump the maven group with 2 updates (#558) @dependabot[bot]
  • Bump com.fasterxml.jackson.core:jackson-core from 2.15.0 to 2.18.11 in /src/it/projects/bom-flattenMode/bom (#539) @dependabot[bot]
  • Bump com.fasterxml.jackson.core:jackson-core from 2.18.6 to 2.18.11 in /src/it/projects/bom-pomElements/bom (#521, #537) @dependabot[bot]

... (truncated)

Commits
  • 329d107 [maven-release-plugin] prepare release 1.9.0
  • 75177b1 Keep Dependabot on Mockito 4
  • b593ea4 Bump com.google.guava:guava in /src/it/projects/bom-pomElements/bom
  • 8a5c2ef fix: initialize CI interpolation for custom POM elements
  • ff5172e Bump the maven group with 2 updates
  • 9e762cd Keep Dependabot on Maven 3.9.x and Resolver 1.9.x
  • 03788e7 Raise IT project prerequisites to Maven 3.9.0
  • 5a6bf5c Declare the Maven artifacts the code uses
  • 79f5df5 Clean up declared dependencies
  • 869985a Use push for PR Automation
  • Additional commits viewable in compare view

Updates com.diffplug.spotless:spotless-maven-plugin from 3.10.4 to 3.11.0

Release notes

Sourced from com.diffplug.spotless:spotless-maven-plugin's releases.

Maven Plugin v3.11.0

Added

  • Add <cleanup>false</cleanup> to <googleJavaFormat> to disable google-java-format's non-whitespace cleanups. (#3157)
  • Add a <maxLineLength> parameter to <googleJavaFormat>. (#3151)
    Overrides the 100-column limit prescribed by the GOOGLE and AOSP styles; requires google-java-format 2.0.0 or later.

Changes

  • Bump default google-java-format version 1.36.1 -> 2.0.0. (#3157)
    This version applies some small non-whitespace cleanups by default (removing redundant semicolons, empty annotation parentheses, and parentheses around single lambda parameters), which can be disabled with <cleanup>false</cleanup>.
Commits
  • 8b62f5a Published maven/3.11.0
  • 8d2edae Published gradle/8.11.0
  • 80977b4 Published lib/4.11.0
  • ed34276 Add maxLineLength option to googleJavaFormat step (requires gjf 2.0.0+) (#3152)
  • b2cd501 docs: split maxLineLength changelog entries into subject and desc style
  • d1c06e2 Update plugin-gradle/README.md
  • 7fd0a54 Update plugin-maven/README.md
  • abe4e9f Merge origin/main: combine cleanup option and gjf 2.0.0 bump with maxLineLength
  • 5ec09c0 Bump google-java-format to 2.0.0 and add a cleanup option (#3157)
  • e8f21cb Handle older google-java-format versions in GoogleJavaFormatStepTest
  • Additional commits viewable in compare view

Updates com.sap.cloud.security:java-bom from 4.3.0 to 4.3.1

Release notes

Sourced from com.sap.cloud.security:java-bom's releases.

4.3.1

  • Retry token, token-key, and OIDC-discovery requests on network errors (token-client, token-client-spring, token-client-spring-3)
    • The retry feature previously only acted on configured HTTP status codes. A network error (connection reset, read timeout, TLS handshake error) was rethrown immediately, so transient network failures during access-token, JWKS, or OIDC-discovery retrieval were never retried — even with retry enabled and maxRetryAttempts configured. In the plain client this surfaced as Error retrieving token keys: null during short identity-service blips.
    • Affected classes now retry on network errors as well, bounded by the existing maxRetryAttempts and retryDelayTime:
      • DefaultOAuth2TokenService, DefaultOAuth2TokenKeyService, DefaultOidcConfigurationService (retry on IOException)
      • XsuaaOAuth2TokenService, SpringOAuth2TokenKeyService, SpringOidcConfigurationService (retry on ResourceAccessException)
    • The Spring variants additionally route retryable HTTP status codes (HttpStatusCodeException) through the same retry handling, so the configured retryStatusCodes now take effect even though RestTemplate surfaces non-2xx responses as exceptions.
    • An already-decided HTTP outcome (OAuth2ServiceException) is still never retried.
    • This aligns the behavior with the documented retry feature, which states that requests failing due to "network issues, such as timeouts or connection errors" are retried.
Changelog

Sourced from com.sap.cloud.security:java-bom's changelog.

4.3.1

  • Retry token, token-key, and OIDC-discovery requests on network errors (token-client, token-client-spring, token-client-spring-3)
    • The retry feature previously only acted on configured HTTP status codes. A network error (connection reset, read timeout, TLS handshake error) was rethrown immediately, so transient network failures during access-token, JWKS, or OIDC-discovery retrieval were never retried — even with retry enabled and maxRetryAttempts configured. In the plain client this surfaced as Error retrieving token keys: null during short identity-service blips.
    • Affected classes now retry on network errors as well, bounded by the existing maxRetryAttempts and retryDelayTime:
      • DefaultOAuth2TokenService, DefaultOAuth2TokenKeyService, DefaultOidcConfigurationService (retry on IOException)
      • XsuaaOAuth2TokenService, SpringOAuth2TokenKeyService, SpringOidcConfigurationService (retry on ResourceAccessException)
    • The Spring variants additionally route retryable HTTP status codes (HttpStatusCodeException) through the same retry handling, so the configured retryStatusCodes now take effect even though RestTemplate surfaces non-2xx responses as exceptions.
    • An already-decided HTTP outcome (OAuth2ServiceException) is still never retried.
    • This aligns the behavior with the documented retry feature, which states that requests failing due to "network issues, such as timeouts or connection errors" are retried.
Commits
  • e2bf023 fix(token-client): retry on network errors across plain + Spring clients (4.3...
  • d4212cf update maven central deployment name (#2067)
  • See full diff in compare view

Updates org.codehaus.mojo:flatten-maven-plugin from 1.8.0 to 1.9.0

Release notes

Sourced from org.codehaus.mojo:flatten-maven-plugin's releases.

1.9.0

Flatten Maven Plugin 1.9.0 fixes CI-friendly property interpolation when custom pomElements are configured, updates its Plexus XML/interpolation dependencies, and cleans up declared Maven dependencies. It requires Maven 3.9.0 or later and Java 8 or later.

✨ Highlights

  • CI-friendly property interpolation with custom <pomElements>: Fixed a bug where configuring custom <pomElements> alongside <flattenMode>resolveCiFriendliesOnly</flattenMode> failed to initialize the CI-friendly property interpolator, leaving ${revision}, ${sha1}, and ${changelist} placeholders unresolved in the flattened POM (#528).
  • Updated Plexus stack: Upgraded plexus-xml to 3.1.0, plexus-utils to 4.1.0, and plexus-interpolation to 1.30.0 (#526, #527, #533).

🚨 Removed

🐛 Bug Fixes

📝 Documentation updates

👻 Maintenance

🔧 Build

📦 Dependency updates

  • Bump com.google.guava:guava from 32.0.0-jre to 33.7.2-jre in /src/it/projects/bom-pomElements/bom (#554, #559) @dependabot[bot]
  • Bump the maven group with 2 updates (#558) @dependabot[bot]
  • Bump com.fasterxml.jackson.core:jackson-core from 2.15.0 to 2.18.11 in /src/it/projects/bom-flattenMode/bom (#539) @dependabot[bot]
  • Bump com.fasterxml.jackson.core:jackson-core from 2.18.6 to 2.18.11 in /src/it/projects/bom-pomElements/bom (#521, #537) @dependabot[bot]

... (truncated)

Commits
  • 329d107 [maven-release-plugin] prepare release 1.9.0
  • 75177b1 Keep Dependabot on Mockito 4
  • b593ea4 Bump com.google.guava:guava in /src/it/projects/bom-pomElements/bom
  • 8a5c2ef fix: initialize CI interpolation for custom POM elements
  • ff5172e Bump the maven group with 2 updates
  • 9e762cd Keep Dependabot on Maven 3.9.x and Resolver 1.9.x
  • 03788e7 Raise IT project prerequisites to Maven 3.9.0
  • 5a6bf5c Declare the Maven artifacts the code uses
  • 79f5df5 Clean up declared dependencies
  • 869985a Use push for PR Automation
  • Additional commits viewable in compare view

Updates com.diffplug.spotless:spotless-maven-plugin from 3.10.4 to 3.11.0

Release notes

Sourced from com.diffplug.spotless:spotless-maven-plugin's releases.

Maven Plugin v3.11.0

Added

  • Add <cleanup>false</cleanup> to <googleJavaFormat> to disable google-java-format's non-whitespace cleanups. (#3157)
  • Add a <maxLineLength> parameter to <googleJavaFormat>. (#3151)
    Overrides the 100-column limit prescribed by the GOOGLE and AOSP styles; requires google-java-format 2.0.0 or later.

Changes

  • Bump default google-java-format version 1.36.1 -> 2.0.0. (#3157)
    This version applies some small non-whitespace cleanups by default (removing redundant semicolons, empty annotation parentheses, and parentheses around single lambda parameters), which can be disabled with <cleanup>false</cleanup>.
Commits
  • 8b62f5a Published maven/3.11.0
  • 8d2edae Published gradle/8.11.0
  • 80977b4 Published lib/4.11.0
  • ed34276 Add maxLineLength option to googleJavaFormat step (requires gjf 2.0.0+) (#3152)
  • b2cd501 docs: split maxLineLength changelog entries into subject and desc style
  • d1c06e2 Update plugin-gradle/README.md
  • 7fd0a54 Update plugin-maven/README.md
  • abe4e9f Merge origin/main: combine cleanup option and gjf 2.0.0 bump with maxLineLength
  • 5ec09c0 Bump google-java-format to 2.0.0 and add a cleanup option (#3157)
  • e8f21cb Handle older google-java-format versions in GoogleJavaFormatStepTest
  • 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 <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

…ates

Bumps the all-maven-dependencies group with 3 updates in the / directory: [com.sap.cloud.security:java-bom](https://github.com/SAP/cloud-security-xsuaa-integration), [org.codehaus.mojo:flatten-maven-plugin](https://github.com/mojohaus/flatten-maven-plugin) and [com.diffplug.spotless:spotless-maven-plugin](https://github.com/diffplug/spotless).
Bumps the all-maven-dependencies group with 3 updates in the /srv directory: [com.sap.cloud.security:java-bom](https://github.com/SAP/cloud-security-xsuaa-integration), [org.codehaus.mojo:flatten-maven-plugin](https://github.com/mojohaus/flatten-maven-plugin) and [com.diffplug.spotless:spotless-maven-plugin](https://github.com/diffplug/spotless).


Updates `com.sap.cloud.security:java-bom` from 4.3.0 to 4.3.1
- [Release notes](https://github.com/SAP/cloud-security-xsuaa-integration/releases)
- [Changelog](https://github.com/SAP/cloud-security-services-integration-library/blob/main/CHANGELOG.md)
- [Commits](SAP/cloud-security-services-integration-library@4.3.0...4.3.1)

Updates `org.codehaus.mojo:flatten-maven-plugin` from 1.8.0 to 1.9.0
- [Release notes](https://github.com/mojohaus/flatten-maven-plugin/releases)
- [Commits](mojohaus/flatten-maven-plugin@1.8.0...1.9.0)

Updates `com.diffplug.spotless:spotless-maven-plugin` from 3.10.4 to 3.11.0
- [Release notes](https://github.com/diffplug/spotless/releases)
- [Changelog](https://github.com/diffplug/spotless/blob/main/CHANGES.md)
- [Commits](diffplug/spotless@maven/3.10.4...maven/3.11.0)

Updates `com.sap.cloud.security:java-bom` from 4.3.0 to 4.3.1
- [Release notes](https://github.com/SAP/cloud-security-xsuaa-integration/releases)
- [Changelog](https://github.com/SAP/cloud-security-services-integration-library/blob/main/CHANGELOG.md)
- [Commits](SAP/cloud-security-services-integration-library@4.3.0...4.3.1)

Updates `org.codehaus.mojo:flatten-maven-plugin` from 1.8.0 to 1.9.0
- [Release notes](https://github.com/mojohaus/flatten-maven-plugin/releases)
- [Commits](mojohaus/flatten-maven-plugin@1.8.0...1.9.0)

Updates `com.diffplug.spotless:spotless-maven-plugin` from 3.10.4 to 3.11.0
- [Release notes](https://github.com/diffplug/spotless/releases)
- [Changelog](https://github.com/diffplug/spotless/blob/main/CHANGES.md)
- [Commits](diffplug/spotless@maven/3.10.4...maven/3.11.0)

---
updated-dependencies:
- dependency-name: com.sap.cloud.security:java-bom
  dependency-version: 4.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: all-maven-dependencies
- dependency-name: org.codehaus.mojo:flatten-maven-plugin
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: all-maven-dependencies
- dependency-name: com.diffplug.spotless:spotless-maven-plugin
  dependency-version: 3.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all-maven-dependencies
- dependency-name: com.sap.cloud.security:java-bom
  dependency-version: 4.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: all-maven-dependencies
- dependency-name: org.codehaus.mojo:flatten-maven-plugin
  dependency-version: 1.9.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all-maven-dependencies
- dependency-name: com.diffplug.spotless:spotless-maven-plugin
  dependency-version: 3.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all-maven-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Nov 10, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants