build(deps): bump eureka-client from 1.9.18 to 2.0.0

[dependabot[bot]]

Bumps eureka-client from 1.9.18 to 2.0.0.

Release notes

Sourced from eureka-client's releases.

2.0.0 Release

Eureka 2.0.0 Release Notes

Eureka 2.0.0 has been released. This release is a new effort and is not related to a previous preview of code released in the 2.x-archive branch which was an experimental re-architecture of Eureka.

The Eureka Server HTTP API and wire data formats have not changed for the 2.0.0 release. Eureka servers and clients should be backwards and forwards compatible over the wire. This release was primarily driven for compatibility with Spring Framework 6.0 and Spring Boot 3.0 and the change to Jakarta EE 9.

What has changed?

The Eureka 2.0.0 Java client API is not backwards compatible with 1.x. Eureka 1.x included support for Jersey 1 and optional Support for Jersey 2. In many cases, Jersey 1 was the default and was baked into the eureka-core and eureka-client modules. Having a default client has been removed. The new eureka-client-jersey3 and eureka-core-jersey3 should now be used if no other implementation is provided (such as Spring Cloud support for a RestTemplate implementation). The DiscoveryClient constructors have been updated to have a new required TransportClientFactories parameter. The majority of the Eureka 2.0.0 Java client API has remained unchanged. All references to javax.* classes have been changed to jakarta.* classes and the appropriate modules have been added. The eureka-server-governator module was removed. There is no current support for the JakartaEE version of @Inject. The eureka-server module currently does not build a functional WAR file. The recommended way of creating a Eureka 2.0.0 server is via Spring Cloud Netflix as a Spring Boot application. The build now requires JDK 11 because of some tests that require Jetty and the version of Jetty that supports Jakarta EE 9 requires Java 11. The build still targets Java 8.

Feedback

Please try things out and provide any feedback or issues at https://github.com/Netflix/eureka/issues.

v2.0.0-rc.4

Candidate release for Spring Cloud 3.0

v2.0.0-rc.3

Candidate release for SpringBoot 3.0 Eureka OSS.

v1.10.18

• xstream 1.4.19 (fixes a CVE) #1472

v1.10.17

• Remove redundant metadata synchronization (#1424) (#1426)
• Update xstream to 1.4.18 (#1421)

v1.10.16

• Enable overriding the client in DiscoveryManager (#1417)
• Refactor: use diamond operator (#1412)
• Refactor: use diamond operator (#1405)
• Allow null values for healthcheck (#1402)

v1.10.15

• Do not log double the URL slash in AbstractJerseyEurekaHttpClient.java (#1401)
• Upgrade xstream to 1.4.17 due to CVE-2021-29505 (#1397)

v1.10.14

• Update Jackson to 2.10 branch (#1393)
• Rotate publishing credentials
• Update ResolverUtils::randomize (#1383)
• Upgrade xstream to 1.4.16 for CVE-2021-213{41-51} (#1386)
• Replace jcenter with maven central (#1381)

... (truncated)

Commits

• b031519 xstream 1.4.19 (#1477)
• 03dc7c7 Merge pull request #1473 from spencergibb/fixme-2-0-patch1
• 3b73bdb Adds TransportClientFactories as required parameter to DiscoveryClient.
• 46dc731 puts original warning log in RetryableEurekaHttpClient
• 05baed7 Re-enable EurekaHttpClientCompatibilityTestSuite.testBasicAuthentication
• c55ebc5 Re-enable ReplicationConcurrencyTest
• d1df09c Re-enable TimeConsumingInstanceRegistryTest
• 5211039 adds test logging
• 84b45cf Updates for servlet based deployment.
• 6e6b05f Creates new EurekaServerHttpClientFactory
• 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 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 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)