Skip to content
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

Upgrade monorepo devDependencies to [email protected] #4406

Closed
wants to merge 3 commits into from

Conversation

trevor-scheer
Copy link
Member

@trevor-scheer trevor-scheer commented Jul 22, 2020

This work is separated out from #4405, and is important to
unblock progress on the new composition format.

This upgrade can happened at any time, leaving this open until we decide to move forward with v15 support.

This comes with a few test updates, mostly around the sorting
of AST nodes (i.e. in the query plan).

This work is separated out from #4405, and is important to
unblock progress on the new composition format.

This upgrade could've happened at any time. Now that composition
is being updated to a fork of the latest graphql schema printer,
v15 is now a requirement.

This comes with a few test updates, mostly around the sorting
of AST nodes (i.e. in the query plan).
@@ -683,7 +683,7 @@ Scenario: for abstract types, it should add __typename when fetching objects of
"kind": "Fetch",
Copy link
Member Author

Choose a reason for hiding this comment

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

@JakeDawkins at this point in time is it acceptable to be updating the .feature file like this? There should be no diff in the actual query plan itself, just in the ordering of some of the nodes.

@trevor-scheer
Copy link
Member Author

It looks like the subscription tests are failing on Node 8 only

@trevor-scheer trevor-scheer marked this pull request as draft July 24, 2020 19:04
@abernix
Copy link
Member

abernix commented Aug 25, 2020

@trevor-scheer Since we're already updating to [email protected] in the release-3.0 branch (by virtue of d3f3efb and e18e0a7 (which are roughly representative fo the same sorts of changes I made on that branch), should/can we close this PR?

Put another way, I don't believe we'll actually land this in 2.x because of the subscriptions tests which started failing similarly on past attempts to do a similar upgrade, e.g., - abernix/graphql-js-v15...abernix/graphql-js-v15-after-devDependency-gets-updated which I attempted/prepared as part of #3712 but never landed for the same subs reasons.

@abernix abernix deleted the trevor/graphql-15-devDependency branch August 25, 2020 18:25
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants