Closed greenkeeper[bot] closed 7 years ago
Update to this version instead π
experimental.const_params=true
set in their .flowconfig
(#1012).The new version differs by 10 commits.
96a869a
0.11.2
275471e
Merge pull request #1012 from graphql/async-map-value-flow
3530f12
Assign rejectCallback to temporary const variable
0f3698c
Add comment to explain redundant null check for rejectCallback
78219d6
Fix flow error in mapAsyncIterator
4a378b9
Merge pull request #1010 from wincent/glh/lint
84e0ad8
Provide more context in lint error message
31ebb1f
Merge pull request #1009 from wincent/glh/header
31cb269
Add linter error preventing use of async
outside the test suite
7b3152f
Add a missing license header
See the full diff
Update to this version instead π
The new version differs by 6 commits.
b84b69f
0.11.3
4fbfd22
Follow up: improve legibility of graphql/execute fns
fee8abb
Revert "Simplify args processing in "graphql" and "execute" functions"
61272b4
Update to flow 0.54 (#1026)
87934f6
Merge pull request #1025 from APIs-guru/simplifyArgs
58ac464
Simplify args processing in "graphql" and "execute" functions
See the full diff
Update to this version instead π
New:
Fixes:
The new version differs by 7 commits.
a501a9c
0.11.4
3afa992
Update to iterall@1.1.2 with memory leak fix
4f5e351
Relicense as MIT (#1046)
eb01a23
Merge pull request #1027 from APIs-guru/excuteArgs
7086160
Fix issues uncovered by enabling Flow
3c74e0b
Add missing '@flow' and unify comments style
56c2e42
Add missing ExecutionArgs export
See the full diff
Update to this version instead π
Update to this version instead π
Fixes:
__proto__
(#1056)
Version 0.11.0 of graphql just got published.
The version 0.11.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of graphql. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 187 commits.
d7a80b6
0.11.0
d3fd6c3
Merge pull request #994 from APIs-guru/cleanupBuildAstSchema
d9178f4
remove dead code from buildASTSchema
0eb070f
Expanded findBreakingChanges test with missing case. (#993)
0779c36
Update subscribe function to return a Promise of AsyncIterator or ExecutionResult (#918)
24a5038
Throw TypeError when coercing an array into a GraphQLString (#925)
85bfd13
Export "ExecutionArgs" type (#988)
26023b3
Adding a type to a union is now a dangerous change. (#991)
6953f97
Freshen yarn.lock
b860b6f
Merge pull request #987 from graphql/greenkeeper/eslint-4.4.1
c156180
chore(package): update eslint to version 4.4.1
b6a46a0
Merge pull request #984 from excitement-engineer/enum-dangerous-change
0e7d460
Freshen yarn.lock
7984f12
Merge pull request #985 from graphql/greenkeeper/eslint-4.4.0
d49c355
Merge pull request #983 from graphql/greenkeeper/chai-4.1.1
There are 187 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: