Update Quarkus Platform and Group to v3.26.3 #2461
Merged
Conversation
This file contains hidden or 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
renovate-bot
changed the title
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
d7bff14 to
b725d37
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
b725d37 to
39c4830
Compare
renovate-bot
changed the title
renovate-bot
changed the title
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
39c4830 to
ce8dc1a
Compare
renovate-bot
changed the title
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
ce8dc1a to
e8f2961
Compare
renovate-bot
changed the title
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
2 times, most recently
from
0178c03 to
a24ad6f
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
a24ad6f to
58ce609
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
58ce609 to
b10d78d
Compare
snazy
added a commit
to snazy/polaris
that referenced
this pull request
Sep 10, 2025
The above test asserts the the log record passed to `org.jboss.logmanager.Logger#logRaw(org.jboss.logmanager.ExtLogRecord)`. For the sake of this test, both the `IcebergJsonProcessingExceptionMapper` and `IcebergExceptionMapper` have a visible-for-testing function `getLogger()` to provide a mocked logger. `getLogger()` however is used for "all the logging", which makes the behavior `verify(JBOSS_LOGGER).logRaw(argThat(...))` "interesting" - the test fails with apache#2461 although no related dependencies have changed in that PR. But eventually the test failure's caused by using `getLogger()` for all logging, which may provide the _wrong_ log record and cause the test to fail. This change renames the `getLogger()` functions to make their special meaning clear, and adds some clarifying comments in the code. Also adding some more test cases for the various exception mapper code paths.
snazy
added a commit
to snazy/polaris
that referenced
this pull request
Sep 10, 2025
The above test asserts the the log record passed to `org.jboss.logmanager.Logger#logRaw(org.jboss.logmanager.ExtLogRecord)`. For the sake of this test, both the `IcebergJsonProcessingExceptionMapper` and `IcebergExceptionMapper` have a visible-for-testing function `getLogger()` to provide a mocked logger. `getLogger()` however is used for "all the logging", which makes the behavior `verify(JBOSS_LOGGER).logRaw(argThat(...))` "interesting" - the test fails with apache#2461 although no related dependencies have changed in that PR. But eventually the test failure's caused by using `getLogger()` for all logging, which may provide the _wrong_ log record and cause the test to fail. This change renames the `getLogger()` functions to make their special meaning clear, and adds some clarifying comments in the code. Also adding some more test cases for the various exception mapper code paths.
snazy
added a commit
that referenced
this pull request
Sep 11, 2025
…2531) The above test asserts the the log record passed to `org.jboss.logmanager.Logger#logRaw(org.jboss.logmanager.ExtLogRecord)`. For the sake of this test, both the `IcebergJsonProcessingExceptionMapper` and `IcebergExceptionMapper` have a visible-for-testing function `getLogger()` to provide a mocked logger. `getLogger()` however is used for "all the logging", which makes the behavior `verify(JBOSS_LOGGER).logRaw(argThat(...))` "interesting" - the test fails with #2461 although no related dependencies have changed in that PR. But eventually the test failure's caused by using `getLogger()` for all logging, which may provide the _wrong_ log record and cause the test to fail. This change renames the `getLogger()` functions to make their special meaning clear, and adds some clarifying comments in the code. Also adding some more test cases for the various exception mapper code paths. Co-authored-by: Alexandre Dutra <[email protected]>
snazy
force-pushed
the
renovate/quarkus-platform-and-group
branch
from
b10d78d to
c973b61
Compare
snazy
approved these changes
Sep 11, 2025
github-project-automation
bot
moved this from PRs In Progress
to Ready to merge
in Basic Kanban Board
github-project-automation
bot
moved this from Ready to merge
to Done
in Basic Kanban Board
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.
This PR contains the following updates:
3.25.4->3.26.33.25.4->3.26.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
quarkusio/quarkus-platform (io.quarkus.platform:quarkus-bom)
v3.26.3Compare Source
v3.26.2Compare Source
v3.26.1Compare Source
v3.26.0Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.