LoginSign Up
← Back to all sparks
E

Eureka

DEVOPS
Velocity5.0

REST-based service registry for resilient load balancing and failover

github.com/Netflix/eureka ↗

Eureka cut its first release in two years, and the notes live in a release candidate, not the tag.

service-discoverymaintenance-modecve-remediationbackportsnetflix-oss
◆Current state
Netflix's Eureka reached v1.10.19 in August 2026 after a candidate train that started in January 2024. The final tag's body is a single CI fix — the JDK setup in the publish workflow — byte-identical to rc.6 before it. The actual accumulated changes sit in rc.4: replacing servo with spectator in the client, EIP support for secondary ENIs, allocation-reduction backports from the 2.x line, VIP address lookup metrics, and xstream upgrades clearing two CVEs.
◆Where it's heading
This is a maintenance-mode project shipping a catch-up release rather than a roadmap. The substantive content is backports and dependency hygiene — the perf work is explicitly ported from 2.x, and the last two candidates exist only to bump xstream and fix the publish pipeline. The 2.0.x line saw its own small patch, so both lines are alive but neither is being extended.
◆Prediction
Direction is hard to read from a feed where the release tag carries less information than its candidates. The pattern suggests further releases will be driven by CVE remediation in transitive dependencies rather than by feature work.

◆Recent moves

  1. 22d ago

    v1.10.19 ships, closing a candidate train opened in 2024

    The v1.10.19 general release, closing a candidate train that ran from January 2024. Its own body records only a JDK fix in the publish workflow — the shipped content is everything accumulated through rc.4, including the servo-to-spectator client migration, allocation reductions backported from 2.x, and xstream CVE upgrades.

    View source ↗
  2. 22d ago

    Candidate six fixes the publish workflow's JDK setup

    The sixth candidate, published the same day as the final tag with an identical one-line body about the publish workflow's JDK setup. A release-plumbing step, not a change users consume.

    View source ↗
  3. 1mo ago

    First movement in two years: perf backports and CVE upgrades

    The candidate that actually carries the 1.10.19 changelog: spectator replaces servo in the client, secondary-ENI EIPs are supported, allocation-reduction work is backported from 2.x, VIP address lookup metrics are added, and xstream moves to 1.4.21 clearing CVE-2022-40151 and CVE-2022-41966.

    View source ↗
  4. 1mo ago

    Candidate five bumps xstream to 1.4.21

    A candidate whose sole change is bumping xstream from 1.4.20 to 1.4.21. Dependency hygiene on the way to the final tag.

    View source ↗
  5. 2y ago

    Two-change patch on the 2.x line

    A two-change patch on the 2.x line avoiding an instance-info copy and upgrading jettison. Shows the 2.x branch is still alive, without indicating it is being developed.

    View source ↗
  6. 2y ago

    Third 1.10.19 candidate, same commit set

    The third 1.10.19 candidate, listing the same ENI and ResponseCacheImpl commits that later appear consolidated in rc.4. Part of the long candidate train rather than a distinct release.

    View source ↗