Skip to content

Conversation

michalvavrik
Copy link
Member

Copy link

quarkus-bot bot commented Feb 17, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit d22295c.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

Copy link
Member

@sberyozkin sberyozkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, though worth waiting for Foivos to have a look

@michalvavrik
Copy link
Member Author

LGTM, though worth waiting for Foivos to have a look

Absolutely, and thanks.

Copy link
Contributor

@zakkak zakkak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a BC expert, but it looks good to me. Thanks @michalvavrik !

@zakkak zakkak merged commit 540fe14 into quarkusio:main Feb 19, 2025
35 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.21 - main milestone Feb 19, 2025
@michalvavrik michalvavrik deleted the feature/fix-bc-provider-in-netty-ssl branch February 19, 2025 09:56
@michalvavrik
Copy link
Member Author

Note that similar code is now present in Netty Handler netty/netty#14855 so we can remove this workaround once Quarkus bumps to 4.1.119.Final.

@gsmet gsmet modified the milestones: 3.21.0.CR1, 3.20.1 Apr 30, 2025
rsvoboda added a commit to rsvoboda/quarkus that referenced this pull request Apr 30, 2025
This reverts code changes from quarkusio#46307, test coverage is kept
@gsmet gsmet modified the milestones: 3.20.1, 3.21.0.CR1 Apr 30, 2025
holly-cummins pushed a commit to holly-cummins/quarkus that referenced this pull request May 6, 2025
This reverts code changes from quarkusio#46307, test coverage is kept
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Private key in PKCS#1 PEM format not working with gRPC in native image
4 participants