Update graphql: 15.4.0 → 15.7.2 (minor) #57
Conversation
This file contains hidden or 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ graphql (15.4.0 → 15.7.2) · Repo
Release Notes
15.7.2
15.7.1
15.7.0
15.6.1
15.6.0
15.5.3
15.5.2
15.5.1
15.5.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 48 commits:
15.7.2GraphQLError: Fixed `originalError.extensions` overriding `extensions` argument to constructor (#3343)15.7.1GraphQLError: revert `originalError` to be nullable (#3341)15.7.0GraphQLError: restore order of enumerable fields (#3335)GraphQLError: keep extensions always present (#3334)GraphQLError: major refactoring to be more in line with v16 (#3333)GraphQLError: fix empty `locations` if error got nodes without locations (#3332)Change type of error extensions from anonymous Record to named interfaces (#3327)15.6.1type/introspection: add missing `__Directive.args(includeDeprecated:)` (#3275)15.6.0Depreacate 'VisitorKeyMap' and backported 'ASTVisitorKeyMap' type (#3267)15.5.3backport: Preserve `deprecationReason` on `GraphQLInputField`s (#3260)Parser: fix function definition of parseArguments and parseArgument (#3254)15.5.2backport parser typescript type-definitions for 15.x.x release (#3251)15.5.1Remove deprecated rmdirSync usage from internal scripts (#3191)Backport instanceOf Error Check Improvements (#3186)15.5.0Fix handling of input objects with 'length' property (#2893)benchmark: fix temp dir creation (#2891)Update deps (#2890)Simplify isAsyncIterable (#2889)Use correct flags for rmdir/mkdir functions (#2886)Update deps (#2884)Replace 'localeCompare' with function independent from locale (#2876)fix: no need to mark param optional if default value is given (#2879)fix: type annotation cannot appear on a constructor declaration (#2878)Extract types for normalized configs into named types (#2868)separateOperations: distinguish query and fragment names (#2859)separateOperations-test: refactor tests to look like snapshots (#2858)introspection: Add missing support for deprecated input values (#2855)introspectionFromSchema: enable 'specifiedByUrl' by default (#2852)tests: update 'getIntrospectionQuery' tests to use custom matchers (#2851)Update deps (#2850)Add tests for supporting Iterable collections across the lib (#2847)README: add instructions on using experimental features (#2849)Update deps (#2844)resources: use named groups in RegExp (#2840)TS: exclude integration tests from root tsconfig.json (#2838)Flow: remove support for measuring Flow coverage (#2837)CI: test on node 15 (#2836)Update deps (#2835)build: add support for experimental releases (#2831)👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands