There's no clean way to resolve this problem without changing the constraints for recipe-core 4.12 branch's dependency on graphql to be 3.8.x-dev || 4.1.x-dev || 4.2.x-dev which is gross and would break our release tool. There is no effective difference between 4 and 4.2 in graphql right now anyway, so if 4 is fine then 4.2 is fine. When we release recipe-core 4.13 we'll test graphql 4.2 against that.
Reverts #45 which was intended to resolve composer conflicts in https://github.com/silverstripe/silverstripe-graphql/actions/runs/4338447240/jobs/7575155226
There's no clean way to resolve this problem without changing the constraints for recipe-core 4.12 branch's dependency on graphql to be
3.8.x-dev || 4.1.x-dev || 4.2.x-devwhich is gross and would break our release tool. There is no effective difference between 4 and 4.2 in graphql right now anyway, so if 4 is fine then 4.2 is fine. When we release recipe-core 4.13 we'll test graphql 4.2 against that.Parent issue