[3.18] 3.18.3 backports 1 #46210
Merged
[3.18] 3.18.3 backports 1 #46210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 09a2733)
(cherry picked from commit be622b8)
This is definitely suboptimal and can lead to infinite loops. Also made some other micro improvements. (cherry picked from commit 80e4bc6)
(cherry picked from commit 1a628af)
(cherry picked from commit 22ff25d)
- follows-up on quarkusio#45771 - fixes quarkusio#46005 (cherry picked from commit d85129e)
So we need to handle it properly. Spotted in: https://github.com/quarkiverse/quarkus-artemis/actions/runs/13150585162/job/36697206471 With stacktrace: ``` Error: ]: Build step io.quarkus.arc.deployment.ConfigBuildStep#validateConfigMappingsInjectionPoints threw an exception: java.lang.NullPointerException: Cannot invoke "org.jboss.jandex.AnnotationTarget.kind()" because "target" is null at io.quarkus.arc.deployment.ConfigBuildStep.validateConfigMappingsInjectionPoints(ConfigBuildStep.java:413) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733) at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856) at io.quarkus.builder.BuildContext.run(BuildContext.java:255) at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18) at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2675) at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2654) at org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1627) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1594) at java.base/java.lang.Thread.run(Thread.java:1583) at org.jboss.threads.JBossThread.run(JBossThread.java:499) at io.quarkus.builder.Execution.run(Execution.java:122) at io.quarkus.builder.BuildExecutionBuilder.execute(BuildExecutionBuilder.java:78) at io.quarkus.deployment.QuarkusAugmentor.run(QuarkusAugmentor.java:161) at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:350) ``` (cherry picked from commit 8c182c0)
(cherry picked from commit d8e18cc)
(cherry picked from commit b07f165)
(cherry picked from commit 3f0d8c5)
…y can be observed from a bean within given context (cherry picked from commit 8336485)
(cherry picked from commit d80e3a9)
Fixes: quarkusio#46136 (cherry picked from commit 575e885)
(cherry picked from commit ab1ae4d)
(cherry picked from commit d674851)
We essentially use Class.forName to load the class instead of the ClassLoader directly, as the former knows how to deal with arrays Fixes: quarkusio#46170 (cherry picked from commit 909bf16)
(cherry picked from commit 0bb909e)
I was hoping to constrain JUnit tests and @QuarkusComponentTests but @QuarkusComponentTest is in another artifact so this will have to do. Related to quarkusio#46035. Note that you can still break things if you specify another priority but that's how it is :). (cherry picked from commit 3b89af2)
The ITs were run as part of the Surefire execution and apparently something is leaking from them. It wasn't an issue before because they were executed at the end of the run but they were executed first with the new orderer given they are not annotated with a Quarkus test annotation. (cherry picked from commit 1abb1b9)
We already have the full path at some point so there's really no need to rebuild it once again, especially since the code was incorrect as it was adding the /q/ prefix always if it wasn't there in the path. It's perfectly valid to not have /q in the path, for instance if you set quarkus.smallrye-health.root-path to /something/else. I added a new test based on the report in addition to the ones we added recently for related fixes. Fixes quarkusio#46040 (cherry picked from commit d8daa71)
Bumps [io.micrometer:micrometer-bom](https://github.com/micrometer-metrics/micrometer) from 1.14.3 to 1.14.4. - [Release notes](https://github.com/micrometer-metrics/micrometer/releases) - [Commits](micrometer-metrics/micrometer@v1.14.3...v1.14.4) --- updated-dependencies: - dependency-name: io.micrometer:micrometer-bom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> (cherry picked from commit ffc972f)
(cherry picked from commit 56cb0cf)
… podman rootless. quarkusio#46190 Signed-off-by: cmoulliard <[email protected]> (cherry picked from commit 5aa8f80)
See https://github.com/vert-x3/wiki/wiki/4.5.13-Release-Notes Fixes the following CVEs: - CVE-2025-24970 - CVE-2025-25193 (cherry picked from commit c07461a)
|
Thanks for your pull request! Your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
quarkus-bot
bot
added
area/arc
quarkus-bot
bot
added
area/core
area/dependencies
|
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
(cherry picked from commit 3a4b8b1)
This comment has been minimized.
This comment has been minimized.
Bumps [io.smallrye:jandex](https://github.com/smallrye/jandex) from 3.2.5 to 3.2.6. - [Release notes](https://github.com/smallrye/jandex/releases) - [Changelog](https://github.com/smallrye/jandex/blob/main/RELEASE_PROCEDURE.md) - [Commits](smallrye/jandex@3.2.5...3.2.6) --- updated-dependencies: - dependency-name: io.smallrye:jandex dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> (cherry picked from commit 5d8df90)
Status for workflow
|
Status for workflow
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please don't merge, I will merge it myself.