Possible support for spago-next

[JulianLeviston]

Hi, first of all, I want to thank you for the incredible work you've put into this library. It’s been a fantastic to use!

The latest Spago is still in alpha, but I’m curious about your thoughts on potentially supporting it. It might be a bit early, but I wanted to understand the process for transitioning to it. Is there maybe a way to support both the old and new versions simultaneously?

A while back I made a fork to support it for my own project which is here if you're interested in taking a look: https://github.com/GetContented/purescript-graphql-client/commits/fix/default-exchanges-and-tests

Thanks again for all your hard work and for considering this!

[bakhtiyarneyman]

I second this. Spago legacy has been broken and it is currently what is blocking me from submitting pull requests against this library.

[CGenie]

I don't get it. There is a spago.yaml file in upstream (https://github.com/OxfordAbstracts/purescript-graphql-client/blob/main/spago.yaml).

Also, apparently, graphql-client should be in package set 60.2.1 (https://github.com/OxfordAbstracts/purescript-graphql-client/blob/main/spago.yaml#L60).

spago registry info graphql-client returns:

...
  9.3.2:
    bytes: 48262
    hash: sha256-7I0sHsTn6IX+fX4EI/GRLo8/z9A2O9GRx3uaPEqzxVQ=
    publishedTime: 2022-12-30T15:22:20.000Z
    ref: v9.3.2

So last version is quite old (we're at 10.0.3 currently). Is it possible to push the new version to spago's package sets?