-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downgrade assertj to 3.21.0 to avoid breaking platform members #23087
Conversation
But aren't they updating to 3.22? |
No, they can't do it currently, AFAIU. |
OK, noted, but that's Kogito. Are we sure we won't break others by downgrading? :) I suppose we can try and see. |
fb02e8d
to
66568fb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I sent an email to the platform coordination list.
thanks folks. We can upgrade when we upgrade to 2.7, but unfortunately we can't right now because of this issue #23076 |
@evacchi let's stay on 3.21.0 for 2.7 too. |
fyi @radtriste |
Failing Jobs - Building 66568fb
Full information is available in the Build summary check run. Failures⚙️ MicroProfile TCKs Tests #- Failing: tcks/microprofile-fault-tolerance
📦 tcks/microprofile-fault-tolerance✖
|
This should be mostly relevant for 2.7. In 2.8 we should look into removing assertj from the quarkus-bom.