Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update apollo graphql packages #12253

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update apollo graphql packages #12253

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 21, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/gateway (source) 2.9.0 -> 2.9.3 age adoption passing confidence
@apollo/gateway (source) 2.8.5 -> 2.9.3 age adoption passing confidence
@apollo/server (source) 4.9.3 -> 4.11.2 age adoption passing confidence
@apollo/subgraph (source) 2.4.8 -> 2.9.3 age adoption passing confidence
@apollo/subgraph (source) 2.2.3 -> 2.9.3 age adoption passing confidence

Release Notes

apollographql/federation (@​apollo/gateway)

v2.9.3

Compare Source

Patch Changes

v2.9.2

Compare Source

Patch Changes

v2.9.1

Compare Source

Patch Changes
apollographql/apollo-server (@​apollo/server)

v4.11.2

Compare Source

(No change; there is a change to the @apollo/server-integration-testsuite used to test integrations, and the two packages always have matching versions.)

v4.11.1

Compare Source

Patch Changes

  • #​7952 bb81b2c Thanks @​glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.

    @apollo/server depends on express which depends on cookie. Versions of express older than v4.21.1 depend on a version of cookie vulnerable to CVE-2024-47764. Users of older express versions who call res.cookie() or res.clearCookie() may be vulnerable to this issue.

    However, Apollo Server does not call this function directly, and it does not expose any object to user code that allows TypeScript users to call this function without an unsafe cast.

    The only way that this direct dependency can cause a vulnerability for users of Apollo Server is if you call startStandaloneServer with a context function that calls Express-specific methods such as res.cookie() or res.clearCookies() on the response object, which is a violation of the TypeScript types provided by startStandaloneServer (which only promise that the response object is a core Node.js http.ServerResponse rather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafe as typecasts in TypeScript.

    However, this upgrade will at least prevent vulnerability scanners from alerting you to this dependency, and we encourage all Express users to upgrade their project's own express dependency to v4.21.1 or newer.

v4.11.0

Compare Source

Minor Changes

  • #​7916 4686454 Thanks @​andrewmcgivery! - Add hideSchemaDetailsFromClientErrors option to ApolloServer to allow hiding 'did you mean' suggestions from validation errors.

    Even with introspection disabled, it is possible to "fuzzy test" a graph manually or with automated tools to try to determine the shape of your schema. This is accomplished by taking advantage of the default behavior where a misspelt field in an operation
    will be met with a validation error that includes a helpful "did you mean" as part of the error text.

    For example, with this option set to true, an error would read Cannot query field "help" on type "Query". whereas with this option set to false it would read Cannot query field "help" on type "Query". Did you mean "hello"?.

    We recommend enabling this option in production to avoid leaking information about your schema to malicious actors.

    To enable, set this option to true in your ApolloServer options:

    const server = new ApolloServer({
  typeDefs,
  resolvers,
  hideSchemaDetailsFromClientErrors: true,
});

v4.10.5

Compare Source

Patch Changes

v4.10.4

Compare Source

Patch Changes
  • #​7871 18a3827 Thanks @​tninesling! - Subscription heartbeats are initialized prior to awaiting subscribe(). This allows long-running setup to happen in the returned Promise without the subscription being terminated prior to resolution.

v4.10.3

Compare Source

Patch Changes
  • #​7866 5f335a5 Thanks @​tninesling! - Catch errors thrown by subscription generators, and gracefully clean up the subscription instead of crashing.

v4.10.2

Compare Source

Patch Changes
  • #​7849 c7e514c Thanks @​TylerBloom! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.

v4.10.1

Compare Source

Patch Changes
  • #​7843 72f568e Thanks @​bscherlein! - Improves timing of the willResolveField end hook on fields which return Promises resolving to Arrays. This makes the use of the setCacheHint method more reliable.

v4.10.0

Compare Source

Minor Changes

  • #​7786 869ec98 Thanks @​ganemone! - Restore missing v1 skipValidation option as dangerouslyDisableValidation. Note that enabling this option exposes your server to potential security and unexpected runtime issues. Apollo will not support issues that arise as a result of using this option.

  • #​7803 e9a0d6e Thanks @​favna! - allow stringifyResult to return a Promise<string>

    Users who implemented the stringifyResult hook can now expect error responses to be formatted with the hook as well. Please take care when updating to this version to ensure this is the desired behavior, or implement the desired behavior accordingly in your stringifyResult hook. This was considered a non-breaking change as we consider that it was an oversight in the original PR that introduced stringifyResult hook.

Patch Changes

v4.9.5

Compare Source

Patch Changes

v4.9.4

Compare Source

Patch Changes

  • #​7747 ddce036e1 Thanks @​trevor-scheer! - The minimum version of graphql officially supported by Apollo Server 4 as a peer dependency, v16.6.0, contains a serious bug that can crash your Node server. This bug is fixed in the immediate next version, [email protected], and we strongly encourage you to upgrade your installation of graphql to at least v16.7.0 to avoid this bug. (For backwards compatibility reasons, we cannot change Apollo Server 4's minimum peer dependency, but will change it when we release Apollo Server 5.)

    Apollo Server 4 contained a particular line of code that makes triggering this crashing bug much more likely. This line was already removed in Apollo Server v3.8.2 (see #​6398) but the fix was accidentally not included in Apollo Server 4. We are now including this change in Apollo Server 4, which will reduce the likelihood of hitting this crashing bug for users of graphql v16.6.0. That said, taking this @apollo/server upgrade does not prevent this bug from being triggered in other ways, and the real fix to this crashing bug is to upgrade graphql.

apollographql/federation (@​apollo/subgraph)

v2.9.3

Compare Source

Patch Changes

v2.9.2

Compare Source

Patch Changes

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

Patch Changes

v2.8.5

Compare Source

Patch Changes

v2.8.4

Compare Source

Patch Changes

v2.8.3

Compare Source

Patch Changes

v2.8.2

Compare Source

Patch Changes

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Patch Changes

v2.7.8

Compare Source

Patch Changes

v2.7.7

Compare Source

Patch Changes

v2.7.6

Compare Source

Patch Changes

v2.7.5

Compare Source

Patch Changes

v2.7.4

Compare Source

Patch Changes

v2.7.3

Compare Source

Patch Changes

v2.7.2

Compare Source

Patch Changes

v2.7.1

Compare Source

Patch Changes

v2.7.0

Compare Source

Minor Changes

  • Implement progressive @override functionality (#​2911)

    The progressive @override feature brings a new argument to the @override directive: label: String. When a label is added to an @override application, the override becomes conditional, depending on parameters provided to the query planner (a set of which labels should be overridden). Note that this feature will be supported in router for enterprise users only.

    Out-of-the-box, the router will support a percentage-based use case for progressive @override. For example:

    type Query {
  hello: String @&#8203;override(from: "original", label: "percent(5)")
}

    The above example will override the root hello field from the "original" subgraph 5% of the time.

    More complex use cases will be supported by the router via the use of coprocessors/rhai to resolve arbitrary labels to true/false values (i.e. via a feature flag service).

Patch Changes

v2.6.3

Compare Source

Patch Changes

v2.6.2

Compare Source

Patch Changes

v2.6.1

Compare Source

Patch Changes

v2.6.0

Compare Source

Patch Changes

v2.5.7

Compare Source

Patch Changes

v2.5.6

Compare Source

Patch Changes

v2.5.5

Compare Source

Patch Changes

  • Fix specific case for requesting __typename on interface entity type (#​2775)

    In certain cases, when resolving a __typename on an interface entity (due to it actual being requested in the operation), that fetch group could previously be trimmed / treated as useless. At a glance, it appears to be a redundant step, i.e.:

    { ... on Product { __typename id }} => { ... on Product { __typename} }

    It's actually necessary to preserve this in the case that we're coming from an interface object to an (entity) interface so that we can resolve the concrete __typename correctly.

  • Updated dependencies []:

v2.5.4

Compare Source

Patch Changes

v2.5.3

Compare Source

Patch Changes

v2.5.2

Compare Source

Patch Changes

v2.5.1

Compare Source

Patch Changes

v2.5.0

Compare Source

Minor Changes

  • Introduce the new @authenticated directive for composition (#​2644)

    Note that this directive will only be fully supported by the Apollo Router as a GraphOS Enterprise feature at runtime. Also note that composition of valid @authenticated directive applications will succeed, but the resulting supergraph will not be executable by the Gateway or an Apollo Router which doesn't have the GraphOS Enterprise entitlement.

    Users may now compose @authenticated applications from their subgraphs into a supergraph. This addition will support a future version of Apollo Router that enables authenticated access to specific types and fields via directive applications.

    The directive is defined as follows:

    directive @&#8203;authenticated on
  | FIELD_DEFINITION
  | OBJECT
  | INTERFACE
  | SCALAR
  | ENUM

    In order to compose your @authenticated usages, you must update your subgraph's federation spec version to v2.5 and add the @authenticated import to your existing imports like so:

    @&#8203;link(url: "https://specs.apollo.dev/federation/v2.5", import: [..., "@&#8203;authenticated"])
Patch Changes

v2.4.13

Compare Source

Patch Changes

v2.4.12

Compare Source

Patch Changes

v2.4.11

Compare Source

Patch Changes

v2.4.10

Compare Source

Patch Changes

v2.4.9

Compare Source

Patch Changes

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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Aug 21, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 4 times, most recently from dd4a427 to 04746e8 Compare August 22, 2023 18:27
@coveralls
Copy link

coveralls commented Aug 22, 2023 •
edited
Loading

Pull Request Test Coverage Report for Build f4287cc7-a9c3-498d-a653-30d1ff1da2f9

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 91.989%
Totals Coverage Status
Change from base Build c488749c-1dd9-4767-af35-a7596161e2ea: 0.0%
Covered Lines: 6809
Relevant Lines: 7402
💛 - Coveralls

@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 6 times, most recently from dc8ae3b to 31b1902 Compare August 30, 2023 15:26
@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.5.3 Aug 31, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 55888cb to 4404776 Compare August 31, 2023 19:08
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.5.3 fix(deps): update apollo graphql packages to v2.5.4 Aug 31, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4404776 to 07257a1 Compare September 18, 2023 21:55
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.5.4 fix(deps): update apollo graphql packages to v2.5.5 Sep 18, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from d55b486 to 0fcb408 Compare September 28, 2023 16:20
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.5.5 fix(deps): update apollo graphql packages Oct 4, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 9e4a6f6 to 95fb173 Compare October 10, 2023 00:37
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from e50dabc to 8b90b4c Compare October 15, 2023 16:50
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 8b90b4c to a7e4d92 Compare October 23, 2023 10:09
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 10, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/32-graphql-federation-schema-first/users-application/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR!   @nestjs/graphql@"12.0.11" from the root project
npm ERR!   peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/apollo
npm ERR!     @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/graphql
npm ERR!     @nestjs/graphql@"12.0.11" from the root project
npm ERR!     peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-21T13_17_50_347Z-debug-0.log
File name: sample/32-graphql-federation-schema-first/posts-application/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR!   @nestjs/graphql@"12.0.11" from the root project
npm ERR!   peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/apollo
npm ERR!     @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/graphql
npm ERR!     @nestjs/graphql@"12.0.11" from the root project
npm ERR!     peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-21T13_17_53_240Z-debug-0.log
File name: sample/32-graphql-federation-schema-first/gateway/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       peer @nestjs/core@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR!       node_modules/@nestjs/apollo
npm ERR!         @nestjs/apollo@"12.0.11" from the root project
npm ERR!       4 more (@nestjs/graphql, @nestjs/platform-express, ...)
npm ERR!     5 more (@nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     peer @nestjs/core@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     peer @nestjs/core@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/graphql
npm ERR!       peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!       node_modules/@nestjs/apollo
npm ERR!         @nestjs/apollo@"12.0.11" from the root project
npm ERR!       1 more (the root project)
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, the root project)
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR!   peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/apollo
npm ERR!     @nestjs/apollo@"12.0.11" from the root project
npm ERR!   @nestjs/graphql@"12.0.11" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/graphql
npm ERR!     peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     @nestjs/graphql@"12.0.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-21T13_17_57_574Z-debug-0.log
File name: sample/31-graphql-federation-code-first/users-application/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"0.2.1" from the root project
npm error   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"10.3.2" from the root project
npm error     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/apollo
npm error       @nestjs/apollo@"12.0.11" from the root project
npm error     5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm error   1 more (@nestjs/core)
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm error node_modules/@nestjs/graphql
npm error   @nestjs/graphql@"12.0.11" from the root project
npm error   peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/apollo
npm error     @nestjs/apollo@"12.0.11" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm error   node_modules/@nestjs/graphql
npm error     @nestjs/graphql@"12.0.11" from the root project
npm error     peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/apollo
npm error       @nestjs/apollo@"12.0.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-21T13_18_00_281Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-21T13_18_00_281Z-debug-0.log

@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from e5922a8 to 3f81ece Compare May 17, 2024 00:57
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 3f81ece to 595b7ce Compare May 29, 2024 06:26
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 595b7ce to 6631771 Compare June 18, 2024 20:19
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 6631771 to edeca72 Compare June 28, 2024 22:47
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from edeca72 to 7652668 Compare July 13, 2024 01:01
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from e0569f5 to e9a32bd Compare July 25, 2024 22:12
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from e9a32bd to 8289203 Compare August 8, 2024 18:59
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 4 times, most recently from 45bd607 to 8c55e68 Compare August 30, 2024 07:21
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from b039e62 to 6ff07a7 Compare September 20, 2024 10:27
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 6ff07a7 to d0eb654 Compare September 27, 2024 04:44
Vue-Pu
Vue-Pu approved these changes Sep 27, 2024
View reviewed changes
Copy link

@Vue-Pu Vue-Pu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge changes As is

@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from d0eb654 to 33efbb2 Compare October 9, 2024 07:16
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from f2d2133 to d3f57b7 Compare October 19, 2024 10:20
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 65ef06f to 485a587 Compare October 30, 2024 02:22
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 4 times, most recently from ee8a076 to f595de2 Compare November 20, 2024 14:47
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from f595de2 to 5871434 Compare November 21, 2024 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Vue-Pu Vue-Pu Vue-Pu approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@coveralls @Vue-Pu