Skip to content

Conversation

@adinauer
Copy link
Member

@adinauer adinauer commented May 23, 2025

#skip-changelog

📜 Description

Use graphql-java v24 for Spring Boot 3.5

💡 Motivation and Context

Compilation error due to v22 of graphql-java being used.

💚 How did you test it?

📝 Checklist

  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

@github-actions
Copy link
Contributor

github-actions bot commented May 23, 2025

Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against ed86e65

Copy link
Collaborator

@lbloder lbloder left a comment

Choose a reason for hiding this comment

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

Minor comment about naming, otherwise LGTM


val graphQlJava = "com.graphql-java:graphql-java:17.3"
val graphQlJava22 = "com.graphql-java:graphql-java:22.1"
val graphQlJavaNew = "com.graphql-java:graphql-java:24.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we go with major versions for the name like before? I.e. graphQlJava24?

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought about it but think it's better to skip the version in the name since we probably want to keep this aligned with Spring Boots required version in the future.

Or it would be even better to have Spring Boot take care of handling the version via its gradle plugin.

@adinauer
Copy link
Member Author

I opted for not bumping the version used in our graphql-java-22 module since that'd require Java 11 instead of Java 8 and also since the module has v22 as its lowest supported version we probably want to keep that.

@adinauer adinauer merged commit 8295b2f into main May 23, 2025
33 of 34 checks passed
@adinauer adinauer deleted the feat/fix-graphql-spring-boot-version branch May 23, 2025 14:52
rbro112 pushed a commit that referenced this pull request May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants