Update peer dependency for latest graphql release #3562
Labels
Comments
hwillson
added
🙏 help-wanted
feature
📚 good-first-issue
ivank
added a commit
to ivank/apollo-client
that referenced
this issue
Jun 19, 2018
So graphql are transitioning to real semver finally. This should fix apollographql#3562 I've set the devDependency to [email protected] 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/)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
warning " > [email protected]" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0".Release candidates are in the npm registry for [email protected], can the peer dependencies be updated?
The text was updated successfully, but these errors were encountered: