Skip to content
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

Upgrade to Netty 4.1.77.FINAL #30892

Closed
Flash1232 opened this issue May 7, 2022 · 1 comment
Closed

Upgrade to Netty 4.1.77.FINAL #30892

Flash1232 opened this issue May 7, 2022 · 1 comment
Labels
status: invalid An issue that we don't feel is valid

Comments

@Flash1232
Copy link

I understand there is a semi-automatic process to update managed dependencies.
In spite of that, we are experiencing inability to use Spring Boot (v2.7.0-RC1) with WebFlux as a whole because of netty/netty#12343 which was just mitigated in https://github.com/netty/netty/releases/tag/netty-4.1.77.Final yesterday. If possible, it would be immensely appreciated to have that updated asap.
I am unsure if a simple version increment would be acceptable as a PR as outlined in your guidelines.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label May 7, 2022
@bclozel
Copy link
Member

bclozel commented May 7, 2022

As stated in the issue template, there is no need to create such issues as we run our dependency upgrades process before the release. This will be taken care of in due time.

Unless the upgrade requires more changes, typically, merging such PRs takes more time or they can be outdated pretty quickly in case of newer releases.

@bclozel bclozel added status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels May 7, 2022
@bclozel bclozel closed this as completed May 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants