-
Notifications
You must be signed in to change notification settings - Fork 311
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
feat: allow graphql@16 as peer dependency #305
Conversation
@jasonkuhrt @GeoffreyHervet could you maybe allow the CI to run so I can at least see if my solution works :) |
@jasonkuhrt As you see some workflows failed because minor snapshot changes with GQL v16. I see two options:
What would be your preference? I would be open to look into both :) |
Snapshots can be given names. I think we can prefix test run with something like |
@jasonkuhrt I ended up using a snapshotResolver to have different snapshots per version. Otherwise the jest would fail because it found obsolete snapshots. I also included a small Let me know what you think and if I need to update anything! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
We can probably drop support for Node 12 in another PR |
@jasonkuhrt could you run the tests again? |
@jasonkuhrt I was being so stupid... I could also just run the workflow on my own brach before asking you... I did that now and they finally pass! So if you approve one last time we should be good to go! |
ty! |
@jasonkuhrt Any idea when this get's published? |
@vdhpieter preview releases are there for every trunk commit. Just published a stable though https://github.com/prisma-labs/graphql-request/releases/tag/3.7.0 |
@jasonkuhrt Thx! just FYI the preview release is broken: https://github.com/prisma-labs/graphql-request/runs/4387187271?check_suite_focus=true |
@vdhpieter yeah, sigh that error is silly |
Closes #299
The other PR was not updated yet, so I tried to give it a go