Micrometer End of Life (EOL) Dates & Support Timeline

Micrometer lifecycle status — the real story

Micrometer, the vendor-neutral application metrics facade for the JVM and the metrics layer of Spring Boot (micrometer-metrics/micrometer on GitHub, Maven coordinates io.micrometer:micrometer-core); one line per minor version. Release days are the Maven Central publish dates from repo1.maven.org/maven2/io/micrometer/micrometer-core (read 2026-09-18), and all 36 first and latest release days match the project GitHub release dates. 1.17 is the current line (1.17.0 on 2026-06-08; latest release 1.17.1, 2026-08-20). 1.18 exists only as a milestone (1.18.0-M1) and is not listed.

End-of-life rule: support dates are the vendor's own, from the Spring generations table (api.spring.io/projects/micrometer/generations, the data behind spring.io/projects/micrometer#support and micrometer.io/support; read twice 2026-09-18, the reads agreed). The mapping is the one used for Spring Boot: eol is the end of open-source support (ossSupportEndDate) and extendedSupport is the end of commercial, enterprise support from Broadcom under Tanzu Spring (commercialSupportEndDate). Spring states these as the last day of a month; it is a month-level policy table. Each Micrometer line is tied to a Spring Boot generation in the same table (1.9 to Spring Boot 2.7, 1.15 to 3.5, 1.16 to 4.0, 1.17 to 4.1), and the two lines Spring marks as extended carry the long commercial window: 1.9 to 2029-06-30 and 1.15 to 2032-06-30. Lines 1.2 and 1.4 are not in the vendor table; micrometer.io/support says release lines it does not list are already end of life, so they are marked end-of-life without a calendar date. On several older lines the last open-source release on Maven Central is dated after the stated end month (1.9.17 shipped 2023-11-13 against an open-source end of 2023-06-30); the vendor's stated date is what is served. The latest version shown for a line is the last open-source release on Maven Central; releases made after that under commercial support are not published there and are not listed.

Commercial context: HeroDevs Never-Ending Support lists Micrometer 1.9.x on the io.micrometer Maven coordinates (26 artifacts including micrometer-bom and micrometer-core, NES version 1.9.17-micrometer-1.9.19, first release 2026-09-17; verified at docs.herodevs.com/micrometer 2026-09-18). That is a commercial offering for the 1.9 line; it is not a project release. Broadcom's own enterprise support for 1.9 runs to 2029-06-30 per the vendor table.

Micrometer release and support pattern

Across the 18 release lines with a published release date, Micrometer has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 1.1 years from its release to its standard-support end date (measured on the 16 lines with both dates published).

Of the 18 release lines tracked, 16 are past end of life and 2 are still within support; 2 are marked end of life without a published date. The newest line, 1.17, was released June 8, 2026. The next scheduled end of life is 1.16 in December 2026 (the vendor names the month only). The longest-supported line currently published is 1.17, to July 2027. Upstream also publishes an extended-support phase for 16 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Micrometer end of life mean for your organization?

When a version of Micrometer reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Micrometer should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Micrometer reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Micrometer version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

Related Products