Skip to content

Conversation

@schaefa
Copy link
Contributor

@schaefa schaefa commented Feb 27, 2023

and make sure MANIFEST.MF is the first entry in the JAR file.
Due to a class loading issue in 20.0 I am going to upgrade to 19.x in Sling Graphql Core and so I back ported the issues fixed in master.

and make sure MANIFEST.MF is the first entry in the JAR file
@dondonz
Copy link
Member

dondonz commented Feb 27, 2023

Hello, thanks for the PR. As a heads up, we haven't yet decided what will be backported or if we will do another v19 release. We typically backport critical security fixes and we decide other fixes on a case by case basis. I will take this PR into consideration at the next release point.

@schaefa
Copy link
Contributor Author

schaefa commented Feb 28, 2023

Right now we (Sling) is having a problem that we cannot use graphql-java out of the box on any versions with the security fix in 17.4 to 20.0 because of that. In addition master has the issue with class loading that prevents us from using 20.x.
So this is, at least for us, a security issue.

@dondonz
Copy link
Member

dondonz commented Mar 14, 2023

To follow up, we will include the fix for the class loading problem #3095 in the next release. Hopefully you'll be able to use 20.1 when it's released

@bbakerman bbakerman merged commit 214d981 into graphql-java:19.x Mar 20, 2023
@dondonz dondonz added this to the 19.4 milestone Mar 22, 2023
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.

3 participants