-
Notifications
You must be signed in to change notification settings - Fork 68
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
Spring Boot 3 Support? #133
Comments
Technically, only one single line needs to change (apart from bumping the dependency versions) to make it compatible with Spring Boot 3 (javax -> jakarta package change). |
That sounds awesome! ❤️ |
Hey @kaqqao - You still working on that? You need a helping hand? |
Any update? |
@kaqqao Any update on this ? As springboot 2.7 is nearing End of Life, upgrade to Springboot 3 is critical for us. |
@kaqqao I see code changes related to Spring Boot 3 has been merged to the main branch.Can you please release a major version also so that we can start pulling that dependency from Maven repo? |
The PR by @SaschaPeukert has been accepted, now we need a new version. |
I... don't know 😓 The version after this will be based on the Spring GraphQL starter, so another major change... |
I don't have issues with 0.x but would vote to go with major release version ie.. 1.0.0 because it follows Semantic Versioning rule |
Do we have breaking changes? Yes, since the java ee namespace is called jakarta now, so the user can't use the new version without changes on his code. So following SemVer it should be "1.0.0". Versions don't cost anything, if the change to Spring GraphQL Starter has breaking changes for the user again, it will be "2.0.0", so what. It's okay I think, Mozilla / Chrome has Versions 100+ and nobody cares 💫 |
Ok. |
Released v1.0.0 |
Anyone knows if we can use graphql-spqr with Spring Boot 3?
Is there any plans on doing that?
Could I maybe help, by just "testing" if this works and pointing out what needs to be changed? Maybe even do some changes?
The text was updated successfully, but these errors were encountered: