You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So graphql are transitioning to real semver finally. This should fixapollographql#3562
I've set the devDependency to graphql@14.0.0-rc.2 to be able to be able
to run the tests on the new version and make sure everything's fine. But
I'm not sure if you think its ok to merge with that release candidate.
Also I think the semver in peerDependencies is more verbose than it
should be:
```js
"peerDependencies": {
"graphql": "^0.11.0 || ^14.0.0"
}
```
This should cover all of the graphql versions from 0.11 and up, since
["^" includes minor and patch
versions](https://bytearcher.com/articles/semver-explained-why-theres-a-caret-in-my-package-json/)
warning " > apollo-client@2.3.2" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0".
Release candidates are in the npm registry for graphql@v14.0.0, can the peer dependencies be updated?
The text was updated successfully, but these errors were encountered: