chore(deps): bump io.fabric8:kubernetes-client-bom from 6.13.4 to 7.6.1

[dependabot]

Bumps io.fabric8:kubernetes-client-bom from 6.13.4 to 7.6.1.

Release notes

Sourced from io.fabric8:kubernetes-client-bom's releases.

7.6.1 (2026-03-05)

Bugs

• Fix #7460: Add explicit Automatic-Module-Name to all httpclient modules to fix invalid auto-derived JPMS module names and vertx/vertx-5 collision

New Contributors

• @​UniZKTech made their first contribution in fabric8io/kubernetes-client#7461

Full Changelog: fabric8io/kubernetes-client@v7.6.0...v7.6.1

7.6.0 (2026-03-02)

Bugs

• Fix #5292: Cluster() configuration should use tlsServerName
• Fix #7174: (httpclient) Fix HTTP client factory priority - VertxHttpClientFactory (default) now has priority -1, OkHttpClientFactory restored to priority 0
• Fix #7174: (httpclient-vertx-5) Add runtime check for Vert.x 5 classes to provide clear error when Vert.x 4/5 conflict occurs
• Fix #7174: (chaos-tests) Fix classpath conflict when testing with Vert.x 5 HTTP client
• Fix #7415: (java-generator) Fix generic type erasure for array of enums with default values
• Fix #7422: (okhttp) Remove internal API usage and fix deprecated OkHttp 5 calls
• Fix #7446: making the timeout of BaseOperation.createOrReplace() configurable

Improvements

• Fix #1105: Add javadoc cross-linking for Fabric8 modules and external dependencies
• Fix #5756: Use Editable interface instead of reflection to instantiate resource builders
• Fix #7422: bump okhttp from 4.12.0 to 5.3.2
• Fix #7252: call additionalConfig when building Vert.x HTTP clients with VertxHttpClientFactory

Dependency Upgrade

• Fix #7374: bump snakeyaml-engine from 2.10 to 3.0.1

New Features

• Fix #7385: Support for Kubernetes v1.35 (Timbernetes)
• Fix #7174: Added Vert.x 5 HTTP client implementation with improved async handling and WebSocket separation
• Fix #7402: Added Byte code level semver API compatibility report generation using Revapi

Note: Breaking changes

• Fix #5756: Resources edited with visitors must now implement io.fabric8.kubernetes.api.builder.Editable. All model classes provided by the client already implement this interface. User-provided custom resources that use visitor-based editing will need to implement Editable (trivial when a builder already exists).
• Fix #7422: bump okhttp from 4.12.0 to 5.3.2. The versions are binary compatible, but the major version upgrade might cause side effects.

Note: Vert.x HTTP Client Compatibility (Issue #7174)

The kubernetes-httpclient-vertx (Vert.x 4.x) and kubernetes-httpclient-vertx-5 (Vert.x 5.x) modules are mutually exclusive. They must not be included together in your project dependencies. Both modules provide an implementation of HttpClient.Factory and use the same io.vertx artifact coordinates but with incompatible major versions.

-Problem*: If both modules are present on the classpath, Maven's dependency resolution may pick Vert.x 4.x JARs while the Vertx5HttpClientFactory is selected at runtime. This causes NoClassDefFoundError for Vert.x 5-specific classes like io.vertx.core.impl.SysProps.

-Solution*: Ensure your project includes only ONE of these modules:

• kubernetes-httpclient-vertx (default, uses Vert.x 4.x) - included transitively via kubernetes-client
• kubernetes-httpclient-vertx-5 (optional, uses Vert.x 5.x) - requires explicit dependency and exclusion of vertx-4

... (truncated)

Changelog

Sourced from io.fabric8:kubernetes-client-bom's changelog.

7.6.1 (2026-03-05)

Bugs

• Fix #7460: Add explicit Automatic-Module-Name to all httpclient modules to fix invalid auto-derived JPMS module names and vertx/vertx-5 collision

7.6.0 (2026-03-02)

Bugs

• Fix #5292: Cluster() configuration should use tlsServerName
• Fix #7174: (httpclient) Fix HTTP client factory priority - VertxHttpClientFactory (default) now has priority -1, OkHttpClientFactory restored to priority 0
• Fix #7174: (httpclient-vertx-5) Add runtime check for Vert.x 5 classes to provide clear error when Vert.x 4/5 conflict occurs
• Fix #7174: (chaos-tests) Fix classpath conflict when testing with Vert.x 5 HTTP client
• Fix #7415: (java-generator) Fix generic type erasure for array of enums with default values
• Fix #7422: (okhttp) Remove internal API usage and fix deprecated OkHttp 5 calls
• Fix #7446: making the timeout of BaseOperation.createOrReplace() configurable

Improvements

• Fix #1105: Add javadoc cross-linking for Fabric8 modules and external dependencies
• Fix #5756: Use Editable interface instead of reflection to instantiate resource builders
• Fix #7422: bump okhttp from 4.12.0 to 5.3.2
• Fix #7252: call additionalConfig when building Vert.x HTTP clients with VertxHttpClientFactory

Dependency Upgrade

• Fix #7374: bump snakeyaml-engine from 2.10 to 3.0.1

New Features

• Fix #7385: Support for Kubernetes v1.35 (Timbernetes)
• Fix #7174: Added Vert.x 5 HTTP client implementation with improved async handling and WebSocket separation
• Fix #7402: Added Byte code level semver API compatibility report generation using Revapi

Note: Breaking changes

• Fix #5756: Resources edited with visitors must now implement io.fabric8.kubernetes.api.builder.Editable. All model classes provided by the client already implement this interface. User-provided custom resources that use visitor-based editing will need to implement Editable (trivial when a builder already exists).
• Fix #7422: bump okhttp from 4.12.0 to 5.3.2. The versions are binary compatible, but the major version upgrade might cause side effects.

Note: Vert.x HTTP Client Compatibility (Issue #7174)

The kubernetes-httpclient-vertx (Vert.x 4.x) and kubernetes-httpclient-vertx-5 (Vert.x 5.x) modules are mutually exclusive. They must not be included together in your project dependencies. Both modules provide an implementation of HttpClient.Factory and use the same io.vertx artifact coordinates but with incompatible major versions.

Problem: If both modules are present on the classpath, Maven's dependency resolution may pick Vert.x 4.x JARs while the Vertx5HttpClientFactory is selected at runtime. This causes NoClassDefFoundError for Vert.x 5-specific classes like io.vertx.core.impl.SysProps.

Solution: Ensure your project includes only ONE of these modules:

• kubernetes-httpclient-vertx (default, uses Vert.x 4.x) - included transitively via kubernetes-client
• kubernetes-httpclient-vertx-5 (optional, uses Vert.x 5.x) - requires explicit dependency and exclusion of vertx-4

When using Vert.x 5, exclude the default Vert.x 4 client and set the vertx.version property:

<properties>
</tr></table> 

... (truncated)

Commits

• 6e7f78b [RELEASE] Updated project version to v7.6.1
• 1c865f1 chore(ci): cancel PR workflows when prerequisite checks fail
• e18bf76 fix(ci): use lax checksums in MAVEN_ARGS for snapshot workflow
• aff7b67 chore(deps): bump central-publishing-maven-plugin from 0.9.0 to 0.10.0
• c65ea82 fix(ci): exclude target directory from Dependabot Maven scanning
• 1c90ff8 fix(ci): use lax checksums for snapshot deploy step
• 921fbfc fix(httpclient): add reactor dependencies to JPMS test module
• 6423874 fix(ci): deploy BOMs separately in snapshot workflow
• 9c786af fix(httpclient): add explicit Automatic-Module-Name to all httpclient modules
• c0d6691 fix: add explicit Automatic-Module-Name to httpclient modules (#7461)
• 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 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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.