chore(deps): update all non-major dependencies #18
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
7830443
to
b8e5511
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
10 times, most recently
from
679502b
to
429e273
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
a79937c
to
3ed9bf4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
cbce856
to
d658855
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
a2005e5
to
4cf712d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
12 times, most recently
from
ef548fe
to
6b70503
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
4041b76
to
e729dc3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
e729dc3
to
87dc971
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. ⚠ Warning: custom changes will be lost. |
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.
This PR contains the following updates:
^4.1.1->^4.3.1^4.1.1->^4.3.1^29.2.2->^29.3.1^5.42.0->^5.48.2^5.42.0->^5.48.2^0.24.5->^0.27.2^8.27.0->^8.32.0^8.5.0->^8.6.0^1.0.1->^1.0.2^29.2.2->^29.3.17.14.2->7.25.1^2.7.1->^2.8.3^29.0.3->^29.0.5^4.8.4->^4.9.4^1.0.1->^1.1.1^0.24.5->^0.27.2Release Notes
apollographql/apollo-server (@apollo/server)
v4.3.1Compare Source
Patch Changes
#7313
ec28b4b33Thanks @vtipparam! - Allow case insensitive lookup on headers. Use HeaderMap instead of plain Map for headers in expressMiddleware.#7311
322b5ebbcThanks @axe-me! - Export intermediate ApolloServerOptions* types#7274
3b0ec8529Thanks @patrick91! - The subgraph spec has evolved in Federation v2 such that the type of_Service.sdl(formerly nullable) is now non-nullable. Apollo Server nowdetects both cases correctly in order to determine whether to:
ApolloServerPluginInlineTracepluginApolloServerPluginSchemaReportingshould not be installedApolloServerPluginUsageReportingis installed and configured with the__onlyIfSchemaIsNotSubgraphoptionv4.3.0Compare Source
Minor Changes
d7e9b9759Thanks @glasser! - If the cache you provide to thepersistedQueries.cacheoption is created withPrefixingKeyValueCache.cacheDangerouslyDoesNotNeedPrefixesForIsolation(new in@apollo/utils.keyvaluecache@2.1.0), theapq:prefix will not be added to cache keys. Providing such a cache tonew ApolloServer()throws an error.Patch Changes
#7232
3a4823e0dThanks @glasser! - Refactor the implementation ofApolloServerPluginDrainHttpServer's grace period. This is intended to be a no-op.#7229
d057e2ffcThanks @dnalborczyk! - Improve compatibility with Cloudflare workers by avoiding the use of the Nodeutilpackage. This change is intended to be a no-op.#7228
f97e55304Thanks @dnalborczyk! - Improve compatibility with Cloudflare workers by avoiding the use of the Nodeurlpackage. This change is intended to be a no-op.#7241
d7e9b9759Thanks @glasser! - For ease of upgrade from the recommended configuration of Apollo Server v3.9+, you can now passnew ApolloServer({ cache: 'bounded' }), which is equivalent to not providing thecacheoption (as a bounded cache is now the default in AS4).v4.2.2Compare Source
Patch Changes
2042ee761Thanks @glasser! - Fix v4.2.0 (#7171) regression where"operationName": null,"variables": null, and"extensions": nullin POST bodies were improperly rejected.v4.2.1Compare Source
Patch Changes
#7187
3fd7b5f26Thanks @trevor-scheer! - Update@apollo/utils.keyvaluecachedependency to the latest patch which correctly specifies its version oflru-cache.Updated dependencies [
3fd7b5f26]:v4.2.0Compare Source
Minor Changes
#7171
37b3b7fb5Thanks @glasser! - If a POST body contains a non-stringoperationNameor a non-objectvariablesorextensions, fail with status code 400 instead of ignoring the field.In addition to being a reasonable idea, this provides more compliance with the "GraphQL over HTTP" spec.
This is a backwards incompatible change, but we are still early in the Apollo Server 4 adoption cycle and this is in line with the change already made in Apollo Server 4 to reject requests providing
variablesorextensionsas strings. If this causes major problems for users who have already upgraded to Apollo Server 4 in production, we can consider reverting or partially reverting this change.#7184
b1548c1d6Thanks @glasser! - Don't automatically install the usage reporting plugin in servers that appear to be hosting a federated subgraph (based on the existence of a field_Service.sdl: String). This is generally a misconfiguration. If an API key and graph ref are provided to the subgraph, log a warning and do not enable the usage reporting plugin. If the usage reporting plugin is explicitly installed in a subgraph, log a warning but keep it enabled.Patch Changes
#7170
4ce738193Thanks @trevor-scheer! - Update @apollo/utils packages to v2 (dropping node 12 support)#7172
7ff96f533Thanks @trevor-scheer! - startStandaloneServer: Restore body-parser request limit to 50mb (as it was in theapollo-serverpackage in Apollo Server 3)#7183
46af8255cThanks @glasser! - Apollo Server tries to detect if execution errors are variable coercion errors in order to give them acodeextension ofBAD_USER_INPUTrather thanINTERNAL_SERVER_ERROR. Previously this would unconditionally set thecode; now, it only sets thecodeif nocodeis already set, so that (for example) custom scalarparseValuemethods can throw errors with specificcodes. (Note that a separate graphql-js bug can lead to these extensions being lost; see https://github.com/graphql/graphql-js/pull/3785 for details.)Updated dependencies [
4ce738193,45856e1dd]:apollographql/apollo-server (@apollo/server-integration-testsuite)
v4.3.1Compare Source
Patch Changes
#7285
35fa72bddThanks @glasser! - Adds an integration test verifying that Rover's introspection query works. This should not break any integration that passes other tests.#7276
15c912f4cThanks @renovate! - Update graphql-http dependencyUpdated dependencies [
ec28b4b33,322b5ebbc,3b0ec8529]:v4.3.0Compare Source
Patch Changes
#7228
f97e55304Thanks @dnalborczyk! - Improve compatibility with Cloudflare workers by avoiding the use of the Nodeurlpackage. This change is intended to be a no-op.Updated dependencies [
3a4823e0d,d057e2ffc,f97e55304,d7e9b9759,d7e9b9759]:v4.2.2Compare Source
Patch Changes
#7203
2042ee761Thanks @glasser! - Fix v4.2.0 (#7171) regression where"operationName": null,"variables": null, and"extensions": nullin POST bodies were improperly rejected.Updated dependencies [
2042ee761]:v4.2.1Compare Source
Patch Changes
#7187
3fd7b5f26Thanks @trevor-scheer! - Update@apollo/utils.keyvaluecachedependency to the latest patch which correctly specifies its version oflru-cache.Updated dependencies [
3fd7b5f26]:v4.2.0Compare Source
Minor Changes
#7171
37b3b7fb5Thanks @glasser! - If a POST body contains a non-stringoperationNameor a non-objectvariablesorextensions, fail with status code 400 instead of ignoring the field.In addition to being a reasonable idea, this provides more compliance with the "GraphQL over HTTP" spec.
This is a backwards incompatible change, but we are still early in the Apollo Server 4 adoption cycle and this is in line with the change already made in Apollo Server 4 to reject requests providing
variablesorextensionsas strings. If this causes major problems for users who have already upgraded to Apollo Server 4 in production, we can consider reverting or partially reverting this change.Patch Changes
#7170
4ce738193Thanks @trevor-scheer! - Update @apollo/utils packages to v2 (dropping node 12 support)#7179
c8129c23fThanks @renovate! - Fix a few tests to support (but not require) TypeScript 4.9.#7171
37b3b7fb5Thanks @glasser! - The integration test suite now incorporates thegraphql-httppackage's audit suite for the "GraphQL over HTTP" specification.#7183
46af8255cThanks @glasser! - Apollo Server tries to detect if execution errors are variable coercion errors in order to give them acodeextension ofBAD_USER_INPUTrather thanINTERNAL_SERVER_ERROR. Previously this would unconditionally set thecode; now, it only sets thecodeif nocodeis already set, so that (for example) custom scalarparseValuemethods can throw errors with specificcodes. (Note that a separate graphql-js bug can lead to these extensions being lost; see https://github.com/graphql/graphql-js/pull/3785 for details.)Updated dependencies [
4ce738193,37b3b7fb5,b1548c1d6,7ff96f533,46af8255c]:facebook/jest
v29.3.1Compare Source
Fixes
[jest-config]Do not warn aboutpresetinProjectConfig(#13583)Performance
[jest-transform]Defer creation of cache directory (#13420)v29.3.0Compare Source
Features
[jest-runtime]Support WebAssembly (Wasm) imports in ESM modules (#13505)Fixes
[jest-config]Add config validation forprojectsoption (#13565)[jest-mock]Treat cjs modules as objects so they can be mocked (#13513)[jest-worker]Throw an error instead of hanging when jest workers terminate unexpectedly (#13566)Chore & Maintenance
[@jest/transform]Updateconvert-source-map(#13509)[docs]MentiontoStrictEqualin UsingMatchers docs. (#13560)typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.48.2Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
v5.48.1Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
v5.48.0Compare Source
Features
5.47.1 (2022-12-26)
Bug Fixes
v5.47.1Compare Source
Bug Fixes
v5.47.0Compare Source
Features
5.46.1 (2022-12-12)
Note: Version bump only for package @typescript-eslint/eslint-plugin
v5.46.1Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
v5.46.0Compare Source
Bug Fixes
objectinstead ofRecord<string, unknown>(#6079) (d91a5fc)Features
5.45.1 (2022-12-05)
Bug Fixes
import type(#6095) (98caa92)ignoreFunctionTypeParameterNameValueShadow(#6129) (9d58b6b)v5.45.1Compare Source
Bug Fixes
import type(#6095) (98caa92)ignoreFunctionTypeParameterNameValueShadow(#6129) (9d58b6b)v5.45.0Compare Source
Bug Fixes
Features
v5.44.0Compare Source
Bug Fixes
parserOptions.projectconfig (#5999) (530e0e6)Features
v5.43.0Compare Source
Bug Fixes
Features
!foo || !foo.baras a valid match for the rule (#5594) (923d486)5.42.1 (2022-11-07)
Bug Fixes
v5.42.1Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.48.2Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.48.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.48.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
5.47.1 (2022-12-26)
Note: Version bump only for package @typescript-eslint/parser
v5.47.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.47.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
5.46.1 (2022-12-12)
Note: Version bump only for package @typescript-eslint/parser
v5.46.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.46.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
5.45.1 (2022-12-05)
Bug Fixes
v5.45.1Compare Source
Bug Fixes
v5.45.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.44.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.43.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
5.42.1 (2022-11-07)
Note: Version bump only for package @typescript-eslint/parser
v5.42.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
vitest-dev/vitest
v0.27.2Compare Source
🚀 Features
🐞 Bug Fixes
coverage.allonly when all tests are run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2665 (85096)🏎 Performance
View changes on GitHub
v0.27.1Compare Source
🚀 Features
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.