-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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 Spring Boot 3.2 #24091
Comments
Should we do a (pre)release with 3.2-RC2 (which has been released today)? @mraible Didn't know about the dev.to jhipster group. Would be more than happy to be added. |
@atomfrede It's a good idea to get some PRs going to see what breaks. I sent you an email with instructions for joining dev.to/jhipster. |
@mraible Can I join too to dev.to? |
@DanielFran You should have an invite in your inbox. |
Can I join dev.to? @mraible |
@BrayanMnz We typically only have committers, but I can certainly add you if you'd like to contribute blog posts to the JHipster community. Please email me at [email protected]. |
Reopening due to missed Kafka regression. This regression blocks every backend dependabot update. |
JHipster has completed the sample check This check uses |
@mshima Is there a failing CI job that shows the issue? |
dependabot with frontend dependencies PRs and dependabot merges will not show the issue. |
I did almost nothing at this issue, you can split between you both. |
@pascalgrimaud bug bounty claimed: https://opencollective.com/generator-jhipster/expenses/178273 |
@DanielFran : approved |
Overview of the issue
According to calendar.spring.io, Spring Boot 3.2 will be released on November 23rd, 2023. We should do a release with 3.2 support before the end of the year. I also think we should do some sort of tribute to the frameworks we're dependent on in a blog post because we're successful because of them. That'd be awesome for Thanksgiving.
Motivation for or Use Case
If you'd like to be a part of https://dev.to/jhipster, please let us know!
The text was updated successfully, but these errors were encountered: