Downgrade Quarkus to 2.3.1.Final #947
Merged
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
gwenneg
force-pushed
the
quarkus-downgrade
branch
3 times, most recently
from
82fad85 to
28d1230
Compare
gwenneg
force-pushed
the
quarkus-downgrade
branch
from
28d1230 to
5239bfb
Compare
bennetelli
approved these changes
Jan 31, 2022
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.
Quarkus 2.6.3.Final caused several exceptions on stage, we can't deploy that version on prod.
I reproduced one of the stage exceptions today, see quarkusio/quarkus#23269.
If we want to deploy notifications on prod next week, we'll need to merge this PR which kind of reverts #926.