[3.10] 3.10.1 backports 2 #40634
Merged
[3.10] 3.10.1 backports 2 #40634
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 b5af823)
(cherry picked from commit c17d757)
…ealth checks per channel (cherry picked from commit e3fc54a)
(cherry picked from commit caa2fad)
(cherry picked from commit fd03b00)
(cherry picked from commit 02fea4a)
(cherry picked from commit 77de608)
Bumps [io.micrometer:micrometer-bom](https://github.com/micrometer-metrics/micrometer) from 1.12.4 to 1.12.5. - [Release notes](https://github.com/micrometer-metrics/micrometer/releases) - [Commits](micrometer-metrics/micrometer@v1.12.4...v1.12.5) --- updated-dependencies: - dependency-name: io.micrometer:micrometer-bom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit a48726a)
(cherry picked from commit ed09ff3)
(cherry picked from commit eb359cd)
The plan is to remove this property in 3.11 but we need to provide a way for people to update to latest security fixes without having to significantly adjust their applications. In 3.11, we need to document this breaking change properly and also provide guidance on how to fix the most common issues that could be encountered due to this breaking change. (cherry picked from commit aa7d2ee)
This to make sure we have a consistent experience between JVM and native modes. (cherry picked from commit 4f372d0)
(cherry picked from commit b16dde5)
…ces` into `quarkus.transaction-manager.unsafe-multiple-last-resources` * The property is now named `quarkus.transaction-manager.unsafe-multiple-last-resources` * It has three possible values: * `allow`: allow unsafe multiple last resources, no warning per offending transaction * `warn`: allow unsafe multiple last resources, one warning log per offending transaction * `fail`: fail on unsafe multiple last resources * It will log a warning on startup if *explicitly* set to `allow` or `warn`. * It defaults to `fail` in this commit. * The plan is to make it default to `warn` in 3.8, which means no log on startup, but one per offending transaction. People will be able to set it to `allow` explicitly to suppress the warning per offending transaction, but will get a warning on startup (since they set the property explicitly). (cherry picked from commit 2595498)
The log level we get in beforeAnalysis may be null, in which case we still want to reset it after analysis. From the javadoc of Logger#getLevel: > Get the log Level that has been specified for this Logger. > The result may be null, which means that this logger's effective level will be inherited from its parent. (cherry picked from commit d5c2ed5)
…o accept `warn-first` and `warn-each` (cherry picked from commit 3b008a8)
Fixes quarkusio#40369 (cherry picked from commit a80a37e)
quarkus-bot
bot
added
area/dependencies
This comment has been minimized.
This comment has been minimized.
|
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@radcortez I tried to backport #40516 to 3.10 and it doesn't fly (see the minimized bot report above). I think I have merged all the other config patches on top of 3.10 so that's odd. Any chance you could have a look? For now, I dropped this commit so that I can release 3.10.1. |
|
Yes, I'll have a look. |
|
I did |
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.