-
-
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.0 #19791
Upgrade to Spring Boot 3.0 #19791
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I'm not sure why these tests are failing when I run
|
…derscoresNamingStrategy
The |
Mongodb + webflux is deadlocking. Happens with any mongodb driver > 4.2.x. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Is it possible to downgrade to an earlier version to solve the problem? |
Maybe. |
I think it's time to disable ci for broken features and merge to the main:
Gateway is still failing with csrf problem. Unless @DanielFran wants to release a alpha with sb2. |
I agree. Let's make sure to create issues for broken features so we can track and add bug bounties to them. I recall seeing something recently about configuring CSRF globally for Spring Cloud Gateway. Do you have a link to the failing job? |
The neo4j microservices workflow #20464. |
I looked into the Neo4j microservices workflow. I created the apps locally and everything seems to start up OK. The e2e test that's failing is the Swagger UI. That does indeed fail in a browser, but I'm not sure it has anything to do with CSRF. In the browser console, it shows a bunch of 404s and a couple 500 errors. The 500s are:
And:
These seem to be caused by Consul. If I change all apps to use
|
sb3: bump elasticseach container to v8.5.0
@mraible @mshima Let's merge this to main. |
Upgrade to Spring Boot 3.0 M5.
Depends on jhipster/jhipster-bom#986. Fixes #19782 and #18198.
To use GitHub packages snapshots, add to
~/.m2/settings.xml
:Use a PAT created at GitHub
Settings/Developer settings/Personal access tokens
withread:packages
permission.Please make sure the below checklist is followed for Pull Requests.