Skip to content

[3.27] Upgrade micrometer to 1.16.6#54836

Closed
jmartisk wants to merge 1 commit into
quarkusio:3.27from
jmartisk:3.27-micrometer-1.16.6
Closed

[3.27] Upgrade micrometer to 1.16.6#54836
jmartisk wants to merge 1 commit into
quarkusio:3.27from
jmartisk:3.27-micrometer-1.16.6

Conversation

@jmartisk

Copy link
Copy Markdown
Contributor

DO NOT MERGE YET, this is still under discussion as to whether this bump is acceptable in a micro release

Fixes the following CVEs:
https://spring.io/security/cve-2026-40983
https://spring.io/security/cve-2026-40984

@jmartisk
jmartisk requested a review from a team June 12, 2026 09:22
@quarkus-bot quarkus-bot Bot added area/dependencies Pull requests that update a dependency file area/metrics labels Jun 12, 2026
@quarkus-bot

quarkus-bot Bot commented Jun 12, 2026

Copy link
Copy Markdown

/cc @brunobat (micrometer), @ebullient (micrometer)

@quarkus-bot

quarkus-bot Bot commented Jun 12, 2026

Copy link
Copy Markdown

/cc @aloubyansky (3.27), @gsmet (3.27), @rsvoboda (3.27)

@quarkus-bot

This comment has been minimized.

@rsvoboda

Copy link
Copy Markdown
Member

https://github.com/micrometer-metrics/micrometer/releases/tag/v1.14.7 is from May 12 2025, so more than one year old.

micrometer-metrics/micrometer@v1.14.7...v1.16.6 shows 1234 commits

@brunobat

Copy link
Copy Markdown
Member

This requires backports.

@brunobat

Copy link
Copy Markdown
Member

I've run the builds for extensions/micrometer-opentelemetry/ and extensions/smallrye-metrics/ locally and they succeed.
This will include new features, especially from:
https://github.com/micrometer-metrics/micrometer/releases/tag/v1.15.0
https://github.com/micrometer-metrics/micrometer/releases/tag/v1.16.0

@quarkus-bot

quarkus-bot Bot commented Jun 16, 2026

Copy link
Copy Markdown

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 2d6a9dc.

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
Native Tests - Windows support Build Failures Logs Raw logs 🔍

You can consult the Develocity build scans.

Failures

⚙️ Native Tests - Windows support #

- Failing: integration-tests/liquibase integration-tests/qute integration-tests/resteasy-jackson 

📦 integration-tests/liquibase

Failed to execute goal io.quarkus:quarkus-maven-plugin:3.27.999-SNAPSHOT:build (default) on project quarkus-integration-test-liquibase: Failed to build quarkus application

📦 integration-tests/qute

Failed to execute goal io.quarkus:quarkus-maven-plugin:3.27.999-SNAPSHOT:build (default) on project quarkus-integration-test-qute: Failed to build quarkus application

📦 integration-tests/resteasy-jackson

Failed to execute goal io.quarkus:quarkus-maven-plugin:3.27.999-SNAPSHOT:build (default) on project quarkus-integration-test-resteasy-jackson: Failed to build quarkus application

@rsvoboda

Copy link
Copy Markdown
Member
2026-06-16T10:37:17.0641230Z Caused by: io.smallrye.common.process.AbnormalExitException: Process exited abnormally (pid 7432) with exit code 20 with error output:
2026-06-16T10:37:17.0641938Z  > Error: Failed to find 'vcvarsall.bat' in a Visual Studio installation.
2026-06-16T10:37:17.0643053Z  > Please make sure that Visual Studio 2022 version 17.1.0 or later is installed on your system. You can download it at https://visualstudio.microsoft.com/downloads/. If this error persists, please try and run GraalVM Native Image in an x64 Native Tools Commad

Windows env issue, @gastaldi is it the same problem you were fixing yesterday?

@jmartisk
jmartisk requested a review from cescoffier June 16, 2026 11:14
@gastaldi

gastaldi commented Jun 16, 2026

Copy link
Copy Markdown
Member

Yes, I provided a fix in graalvm/setup-graalvm#221

UPDATE: actually no, this is something else

UPDATE: Actually yes, it is related. That PR should now fix it. I created #54908 which should be backported to fix that

@cescoffier

Copy link
Copy Markdown
Member

If @brunobat is ok with it, I'm ok.

@brunobat

brunobat commented Jun 16, 2026

Copy link
Copy Markdown
Member

Yes, this is the most practical path. The only alternative would be to cherry-pick the CVE fixes and perform a custom release of Micrometer.

@jmartisk jmartisk added this to the 3.27.5 milestone Jul 1, 2026
@jmartisk jmartisk moved this to 3.27.5 in Backports for 3.27 Jul 1, 2026
@jmartisk jmartisk removed this from the 3.27.5 milestone Jul 1, 2026
@jmartisk

jmartisk commented Jul 1, 2026

Copy link
Copy Markdown
Contributor Author

It was decided to skip this upgrade in the end.

@jmartisk jmartisk closed this Jul 1, 2026
@quarkus-bot quarkus-bot Bot added the triage/invalid This doesn't seem right label Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/dependencies Pull requests that update a dependency file area/metrics triage/flaky-test triage/invalid This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants