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.

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

fix(deps): update dependency @graphql-mesh/runtime to v0.105.18 #729

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-mesh/runtime (source) 0.17.0 -> 0.105.18 age adoption passing confidence

Release Notes

ardatan/graphql-mesh (@​graphql-mesh/runtime)

v0.105.18

Compare Source

Patch Changes

v0.105.17

Compare Source

Patch Changes

v0.105.16

Compare Source

Patch Changes

v0.105.15

Compare Source

Patch Changes

v0.105.14

Compare Source

Patch Changes

v0.105.13

Compare Source

Patch Changes

v0.105.12

Compare Source

Patch Changes

v0.105.11

Compare Source

Patch Changes

v0.105.10

Compare Source

Patch Changes

v0.105.9

Compare Source

Patch Changes

v0.105.8

Compare Source

Patch Changes

v0.105.7

Compare Source

Patch Changes

v0.105.6

Compare Source

Patch Changes

v0.105.5

Compare Source

Patch Changes

v0.105.4

Compare Source

Patch Changes

v0.105.2

Compare Source

Patch Changes

v0.105.1

Compare Source

Patch Changes

v0.105.0

Compare Source

Patch Changes

v0.104.2

Compare Source

Patch Changes

v0.104.1

Compare Source

Patch Changes

v0.104.0

Compare Source

Minor Changes

v0.103.12

Compare Source

Patch Changes

v0.103.11

Compare Source

Patch Changes

v0.103.10

Compare Source

Patch Changes

v0.103.9

Compare Source

Patch Changes

v0.103.8

Compare Source

Patch Changes

v0.103.7

Compare Source

Patch Changes

v0.103.6

Compare Source

Patch Changes

v0.103.5

Compare Source

Patch Changes

v0.103.4

Compare Source

Patch Changes

v0.103.3

Compare Source

Patch Changes

v0.103.2

Compare Source

Patch Changes

v0.103.1

Compare Source

Patch Changes

v0.103.0

Compare Source

Patch Changes

v0.102.0

Compare Source

Patch Changes

v0.101.0

Compare Source

Patch Changes

v0.100.8

Compare Source

Patch Changes

v0.100.7

Compare Source

Patch Changes

v0.100.6

Compare Source

Patch Changes

v0.100.5

Compare Source

Patch Changes

v0.100.4

Compare Source

Patch Changes

v0.100.3

Compare Source

Patch Changes

v0.100.2

Compare Source

Patch Changes

v0.100.1

Compare Source

Patch Changes

v0.100.0

Compare Source

Patch Changes

v0.99.12

Compare Source

Patch Changes

v0.99.11

Compare Source

Patch Changes
  • #​7145
    7544594
    Thanks @​Author, @​User! - New Federation
    Composition Approach for the new Mesh v1 alpha; (If you are using Mesh v0 legacy, ignore this
    changelog)

    Now Mesh Compose produces a superset of Federated Supergraph.

    • Drop any options and implementation related to the old fusiongraph
      • The output is a valid supergraph that can be consumed by any Federation router. But if it is
        not Mesh Serve, the subgraph should still be served via Mesh Serve then consumed by that
        Federation router. If it is Mesh Serve, no additional server is needed because Mesh Serve
        already knows the additional directives etc of the transports
    • Compose the subgraphs using @theguild/federation-composition package
      • So benefit from the validation rules of Federation in Mesh Compose
    • Ability to consume existing federated subgraphs
      • Since the composition is now Federation, we can accept any federated subgraph
    • Implement Federation transform to transform any subgraph to a federated subgraph by adding
      Federation directives (v2 only) . This is on user's own because they add the directives
      manually. And for __resolveReference, we use @merge directive to mark a root field as an
      entity resolver for Federation
    • Use additional @source directive to consume transforms on the subgraph execution (field
      renames etc)
    • Use additional @resolveTo directive to consume additional stitched resolvers
    • Use additional @transport directive to choose and configure a specific transport for subgraphs
    • Handle unsupported additional directives with another set of additional directives on Query
      for example directives on unions, schema definitions, enum values etc and then
      @extraUnionDirective added with missing directives for unions then on the runtime these
      directives are added back to the union for the subgraph execution of the transports.

    Basically Mesh Compose uses Federation spec for composition, validation and runtime BUT the output
    is a superset with these additional directives imported via @composeDirective;

    • @merge (Taken from Stitching Directives) If a custom entity resolver is defined for a root
      field like below, the gateway will pick it up as an entity resolver;
    type Query {
       fooById(id: ID!): Foo @​merge(keyField: 'id', keyArg: 'id', subgraph: Foo)
    }
    • @resolveTo (Taken from v0) This allows to delegate to a field in any subgraph just like Schema
      Extensions in old Schema Stitching approach;
        extend type Book {
    
            @​resolveTo(
              sourceName: "authors"
              sourceTypeName: "Query"
              sourceFieldName: "authors"
              keyField: "authorId"
              keysArg: "ids"
            )
        }
    • @source Taken from Fusion This allows us to know how the original definition is in the
      subgraph. If this directive exists, the runtime applies the transforms from Schema Stitching
      during the subgraph execution. This directive can exist in arguments, fields, types etc.
    type Query {
     @​source(type: "MyUser") # This means `User` is actually `MyUser` in the actual subgraph
    }
    
    type User @​source(name: "MyUser") {
      id: ID
      name: String
    }
    • @transport Taken from Fusion This allows us to choose a specific transport (rest, mysql,
      graphql-ws, graphql-http etc) for the subgraph execution with some configuration. In the
      runtime, the gateway loads the transports and passes the subgraph schema with annotations if
      needed to get an executor to execute queries against that subgraph.
    schema @&#8203;transport(subgraph: "API", kind: "rest", location: "http://0.0.0.0:<api_port>") {
      query: Query
      mutation: Mutation
      subscription: Subscription
    }
    • @extraSchemaDefinitionDirective By default, it is not possible to add directives from subgraph
      to the supergraph but it is possible to do the same thing on types or fields. So we add this
      directive to Query for the directives we want to add to the schema. Then the runtime picks
      those per subgraph to put the directives back to their original places;
    type Query @&#8203;extraSchemaDefinitionDirective(
      directives: {transport: [{subgraph: "petstore", kind: "rest", location: "http://0.0.0.0:<petstore_port>/api/v3"}]}
    )  {
    • @extraEnumValueDirective and @extraTypeDirective Same for enum values and unions etc that
      are not supported by the composition library

    Thanks to these directives, subgraphs can be published individually to Hive for example then the
    supergraph stored there can be handled by Mesh Gateway since the composition is the same. All
    the additions etc are done on the subgraph level. For the Fed gateways except Mesh Serve,
    subgraphs can be served individually by Mesh Serve again while they are consumed by any gw like
    Apollo Router Shareable is enabled by default for non-federated subgraphs

    Documentation PR has details for users; [https://github.com/v1 Docs Draft ardatan/graphql-mesh#7109](https://redirect.github.com/ard


Configuration

📅 Schedule: Branch creation - "* * * * 0,6" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 force-pushed the renovate/graphql-mesh-runtime-0.x branch from 80861f9 to 01046fb Compare February 28, 2024 16:51
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.97.7 fix(deps): update dependency @graphql-mesh/runtime to v0.98.0 Feb 28, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 01046fb to 656acea Compare March 13, 2024 20:31
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.98.0 fix(deps): update dependency @graphql-mesh/runtime to v0.98.3 Mar 13, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 656acea to 90db2da Compare March 14, 2024 15:04
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.98.3 fix(deps): update dependency @graphql-mesh/runtime to v0.98.4 Mar 14, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 90db2da to 4417e28 Compare March 22, 2024 17:40
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.98.4 fix(deps): update dependency @graphql-mesh/runtime to v0.98.6 Mar 22, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 4417e28 to faa99f8 Compare March 31, 2024 05:08
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.98.6 fix(deps): update dependency @graphql-mesh/runtime to v0.98.7 Mar 31, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from faa99f8 to 1e96bef Compare April 8, 2024 16:58
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.98.7 fix(deps): update dependency @graphql-mesh/runtime to v0.98.8 Apr 8, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 1e96bef to 9b7493f Compare April 26, 2024 22:06
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.98.8 fix(deps): update dependency @graphql-mesh/runtime to v0.99.0 Apr 26, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 9b7493f to c573662 Compare April 29, 2024 11:49
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.0 fix(deps): update dependency @graphql-mesh/runtime to v0.99.1 Apr 29, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from c573662 to 1c5c2c9 Compare April 29, 2024 14:27
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.1 fix(deps): update dependency @graphql-mesh/runtime to v0.99.2 Apr 29, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 1c5c2c9 to 63c9f51 Compare April 30, 2024 19:15
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.2 fix(deps): update dependency @graphql-mesh/runtime to v0.99.3 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 63c9f51 to a289213 Compare May 8, 2024 14:57
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.3 fix(deps): update dependency @graphql-mesh/runtime to v0.99.5 May 8, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from a289213 to 36889d5 Compare May 22, 2024 12:04
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.5 fix(deps): update dependency @graphql-mesh/runtime to v0.99.6 May 22, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 36889d5 to 4af8abf Compare May 27, 2024 11:01
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.6 fix(deps): update dependency @graphql-mesh/runtime to v0.99.7 May 27, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 4af8abf to e592f4a Compare June 9, 2024 08:52
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.99.7 fix(deps): update dependency @graphql-mesh/runtime to v0.99.8 Jun 9, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from e592f4a to 1c4d145 Compare June 20, 2024 17:15
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.102.0 fix(deps): update dependency @graphql-mesh/runtime to v0.103.6 Sep 8, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 9346595 to 5aa66f8 Compare October 20, 2024 08:48
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.103.6 fix(deps): update dependency @graphql-mesh/runtime to v0.103.8 Oct 20, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 5aa66f8 to 6effbc5 Compare November 3, 2024 15:19
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.103.8 fix(deps): update dependency @graphql-mesh/runtime to v0.103.12 Nov 3, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 6effbc5 to e5050d5 Compare November 10, 2024 08:55
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.103.12 fix(deps): update dependency @graphql-mesh/runtime to v0.104.1 Nov 10, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from e5050d5 to 440e2d2 Compare November 17, 2024 08:49
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.104.1 fix(deps): update dependency @graphql-mesh/runtime to v0.104.2 Nov 17, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 440e2d2 to 519b75d Compare November 24, 2024 12:26
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.104.2 fix(deps): update dependency @graphql-mesh/runtime to v0.105.1 Nov 24, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 519b75d to 90dda18 Compare December 1, 2024 08:53
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.1 fix(deps): update dependency @graphql-mesh/runtime to v0.105.5 Dec 1, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 90dda18 to 212425e Compare December 8, 2024 14:58
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.5 fix(deps): update dependency @graphql-mesh/runtime to v0.105.6 Dec 8, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 212425e to 4d3115a Compare December 15, 2024 04:31
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.6 fix(deps): update dependency @graphql-mesh/runtime to v0.105.8 Dec 15, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 4d3115a to 59cbeb7 Compare December 23, 2024 00:08
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.8 fix(deps): update dependency @graphql-mesh/runtime to v0.105.9 Dec 23, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 59cbeb7 to 378f306 Compare December 30, 2024 00:01
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.9 fix(deps): update dependency @graphql-mesh/runtime to v0.105.10 Dec 30, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 378f306 to 162603f Compare January 1, 2025 20:23
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.10 fix(deps): update dependency @graphql-mesh/runtime to v0.105.11 Jan 1, 2025
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from 162603f to ace87be Compare January 11, 2025 15:29
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.11 fix(deps): update dependency @graphql-mesh/runtime to v0.105.12 Jan 11, 2025
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from ace87be to ea35752 Compare January 25, 2025 12:08
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.12 fix(deps): update dependency @graphql-mesh/runtime to v0.105.13 Jan 25, 2025
@renovate renovate bot force-pushed the renovate/graphql-mesh-runtime-0.x branch from ea35752 to 278fd67 Compare February 16, 2025 14:12
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/runtime to v0.105.13 fix(deps): update dependency @graphql-mesh/runtime to v0.105.18 Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants