graphql@0.9.6 breaks build 🚨 #83
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
graphql just published its new version 0.9.6.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As graphql is “only” a peerDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
New
GRAPHQL_NO_NAME_WARNINGenvironment variable. This may be useful when working with legacy schemas.The new version differs by 436 commits .
3c0a5360.9.6bcbab0fRegenerate yarn.lock7ddd8ddMerge pull request #839 from graphql/no-name-warning04e368bKill errant blank line163fbb4Add tests for assertValidName423200f[RFC] Environment var to silence warning about invalid names.90336850.9.55b06511Merge pull request #836 from graphql/fix-832b013e73Allow for nullish values when defining enumsd7fe661Merge pull request #695 from graphql/type-checks333c248Use flow %checks to reduce occurance of :anya9d1f20Refresh yarn.lock6e8d57dMerge pull request #835 from graphql/greenkeeper/iterall-1.1.16e3494dMerge pull request #807 from APIs-guru/visitore37b8bcMerge pull request #831 from graphql/greenkeeper/coveralls-2.13.1There are 250 commits in total. See the full diff.