Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

fix(deps): update apollo graphql packages #221

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 27, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/server-plugin-landing-page-graphql-playground (source) 4.0.0 -> 4.0.1 age adoption passing confidence
@apollo/server-plugin-response-cache (source) 4.1.0 -> 4.1.3 age adoption passing confidence
@apollo/subgraph (source) 2.3.2 -> 2.7.0 age adoption passing confidence
@apollo/utils.keyvadapter (source) 3.0.0 -> 3.1.0 age adoption passing confidence

Release Notes

apollographql/apollo-server (@​apollo/server-plugin-landing-page-graphql-playground)

v4.0.1

Compare Source

Patch Changes
apollographql/apollo-server (@​apollo/server-plugin-response-cache)

v4.1.3

Compare Source

Patch Changes
  • #​7614 4fadf3ddc Thanks @​Cellule! - Publish TypeScript typings for CommonJS modules output.

    This allows TypeScript projects that use CommonJS modules with
    moduleResolution: "node16" or
    moduleResolution: "nodeNext"
    to correctly resolves the typings of apollo's packages as CommonJS instead of ESM.

v4.1.2

Compare Source

Patch Changes

v4.1.1

Compare Source

Patch Changes
apollographql/federation (@​apollo/subgraph)

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 @​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 @​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:

    @​link(url: "https://specs.apollo.dev/federation/v2.5", import: [..., "@​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

v2.4.8

Compare Source

Patch Changes

v2.4.7

Compare Source

Patch Changes

v2.4.6

Compare Source

Patch Changes

v2.4.5

Compare Source

Patch Changes

v2.4.4

Compare Source

Patch Changes

v2.4.3

Compare Source

Patch Changes
  • Resolve Promise references before calling __resolveType on interface (#​2556)

    Since the introduction of entity interfaces, users could not return
    a Promise from __resolveReference while implementing a synchronous,
    custom __resolveType function. This change fixes/permits this use case.

    Additional background / implementation details:

    Returning a Promise from __resolveReference has historically never
    been an issue. However, with the introduction of entity interfaces, the
    calling of an interface's __resolveType function became a new concern.

    __resolveType functions expect a reference (and shouldn't be concerned
    with whether those references are wrapped in a Promise). In order to
    address this, we can await the reference before calling the
    __resolveType (this handles both the non-Promise and Promise case).

  • Updated dependencies [f6a8c1ce]:

v2.4.2

Compare Source

Patch Changes

v2.4.1

Compare Source

Patch Changes

v2.4.0

Compare Source

Patch Changes

v2.3.6

Compare Source

Patch Changes

v2.3.5

Compare Source

Patch Changes

v2.3.4

Compare Source

Patch Changes

v2.3.3

Compare Source

Patch Changes
apollographql/apollo-utils (@​apollo/utils.keyvadapter)

v3.1.0

Compare Source

Minor Changes
  • #​337 e02f708 Thanks @​HishamAli81! - Updated the KeyValueCache.KeyValueCacheSetOptions type to be configurable, to be able to support custom key value caches that require additional cache set options.
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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner May 27, 2023 20:19
@renovate renovate bot requested review from jpetto and sri-kirsh May 27, 2023 20:19
@renovate renovate bot added the dependencies Pull requests that update a dependency file label May 27, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 8 times, most recently from f379733 to f762037 Compare June 5, 2023 22:01
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 8 times, most recently from dd66ab1 to 568d13a Compare June 13, 2023 15:07
@renovate renovate bot changed the title fix(deps): update dependency @apollo/server-plugin-landing-page-graphql-playground to v4.0.1 fix(deps): update apollo graphql packages Jun 13, 2023
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 8 times, most recently from 8ce0501 to c2659de Compare June 20, 2023 21:58
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 8 times, most recently from 850a7cc to 0e09449 Compare August 14, 2023 09:21
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 5 times, most recently from fd7b552 to 70fb851 Compare August 30, 2023 21:45
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 70fb851 to 477052e Compare September 1, 2023 18:08
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 9e2eb07 to a274255 Compare September 15, 2023 15:27
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from a274255 to 5c478b0 Compare September 19, 2023 21:30
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 96610dc to 1f70083 Compare October 9, 2023 09:39
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 1f70083 to 3c101de Compare October 14, 2023 22:45
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 3c101de to 0ad4927 Compare October 23, 2023 15:14
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 2f8675b to 0042eab Compare November 18, 2023 00:30
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 0042eab to e745fc2 Compare November 29, 2023 00:16
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from e745fc2 to 864a539 Compare December 12, 2023 23:02
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 864a539 to 122e288 Compare January 12, 2024 16:32
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 122e288 to ef39c0b Compare January 21, 2024 03:08
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from ef39c0b to 6157e71 Compare January 22, 2024 23:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants