Mesh
On this page

@graphql-mesh/transport-soap

Changelog for @graphql-mesh/transport-soap: every release with its changes and the pull requests behind them.

0.13.1

Patch Changes

  • Updated dependencies [c7f0f3f, c7f0f3f]:
    • @graphql-mesh/types@0.107.1
    • @graphql-mesh/utils@0.107.1

0.13.0

Patch Changes

  • Updated dependencies [ab73b38, 51b15f4]:
    • @graphql-mesh/types@0.107.0
    • @graphql-mesh/utils@0.107.0

0.12.0

Patch Changes

0.11.1

Patch Changes

0.11.0

Patch Changes

0.10.47

Patch Changes

  • #9465 eece882 Thanks @zcag! - dependencies updates:

  • #9527 59a2e76 Thanks @dependabot! - dependencies updates:

  • #9530 6282a71 Thanks @dependabot! - dependencies updates:

  • #9547 b28d9ec Thanks @dependabot! - dependencies updates:

  • #9558 cfa9cd9 Thanks @dependabot! - dependencies updates:

  • #9477 cd30910 Thanks @zcag! - Fix query args taking priority over soapHeaders loader config in namespace-aware SOAP executor.

    When both a WSDL-declared <soap:header> arg and the loader-level soapHeaders config contribute content to the same XML header element, the config entry previously ran last and silently overwrote the value supplied by the caller.

    The fix seeds soap:Header from the soapHeaders config first, then lets the args loop overwrite on key collision — so explicit query arguments always take priority over static loader defaults. Args that GraphQL coerces to an empty/absent value (null, undefined, "", or {}) are not treated as intentional overrides and leave the config-supplied default in place.

  • #9465 eece882 Thanks @zcag! - Correct SOAP envelope generation for WSDLs with multiple XSD namespaces and <soap:header> bindings, and fix array serialization.

    Three issues are addressed together because they all surface on the same class of WSDL (one operation, multiple XSD schemas, header binding, array-typed parts):

    • XML namespace — every body element used to be qualified with the WSDL bindingNamespace. Now each element gets the namespace of the schema where it is declared, so types that come from a different XSD render under their own prefix.
    • <soap:header> binding — message parts the WSDL routes to <soap:Header> were being placed inside <soap:Body>. The loader now records header parts on the @soap directive and the executor splits them into <soap:Header> at request time.
    • Arrays — array-valued args were iterated with for..in, producing numeric child elements (<prefix:0>, <prefix:1>). They now serialize as repeated sibling elements.

    The new namespace-aware path activates only when the schema was built by the updated loader (it now exposes a typeNamespaceMap on schema.extensions and a per-arg namespace map on the @soap directive) and bodyAlias is not configured. Schemas built by older loader versions, and any usage that sets bodyAlias, continue to use the legacy code path unchanged. For single-namespace WSDLs without bodyAlias the new path falls back to the same body prefix the legacy path used, preserving byte-for-byte compatibility (covered by a regression test against tempconvert.wsdl).

  • Updated dependencies [eece882, 6282a71, b28d9ec, eece882, eece882, 59a2e76, 6282a71, b28d9ec, 1b0e3c4, eece882, 444fbbe, 6282a71, 2c347d5, b28d9ec, 1b0e3c4, 4c56adc]:

    • @graphql-mesh/cross-helpers@0.4.15
    • @graphql-mesh/string-interpolation@0.5.18
    • @graphql-mesh/types@0.104.30
    • @graphql-mesh/utils@0.104.38

0.10.46

Patch Changes

0.10.45

Patch Changes

0.10.44

Patch Changes

0.10.43

Patch Changes

0.10.42

Patch Changes

0.10.41

Patch Changes

0.10.40

Patch Changes

0.10.39

Patch Changes

  • Updated dependencies [95a2d10, 95a2d10]:
    • @graphql-mesh/types@0.104.26
    • @graphql-mesh/utils@0.104.34

0.10.38

Patch Changes

0.10.37

Patch Changes

  • Updated dependencies [94fbfbd]:
    • @graphql-mesh/string-interpolation@0.5.16
    • @graphql-mesh/utils@0.104.32

0.10.36

Patch Changes

  • Updated dependencies [339c32c]:
    • @graphql-mesh/string-interpolation@0.5.15
    • @graphql-mesh/utils@0.104.31

0.10.35

Patch Changes

  • Updated dependencies [3ad6a00]:
    • @graphql-mesh/string-interpolation@0.5.14
    • @graphql-mesh/utils@0.104.30

0.10.34

Patch Changes

0.10.33

Patch Changes

  • Updated dependencies [300aea0, 300aea0]:
    • @graphql-mesh/types@0.104.25
    • @graphql-mesh/utils@0.104.28

0.10.32

Patch Changes

0.10.31

Patch Changes

0.10.30

Patch Changes

0.10.29

Patch Changes

  • Updated dependencies [4f81520]:
    • @graphql-mesh/types@0.104.23
    • @graphql-mesh/utils@0.104.25

0.10.28

Patch Changes

0.10.27

Patch Changes

0.10.26

Patch Changes

0.10.25

Patch Changes

  • Updated dependencies [d213cd9, d213cd9]:
    • @graphql-mesh/types@0.104.21
    • @graphql-mesh/utils@0.104.23

0.10.24

Patch Changes

0.10.23

Patch Changes

0.10.22

Patch Changes

0.10.21

Patch Changes

  • Updated dependencies [30e8e32]:
    • @graphql-mesh/string-interpolation@0.5.10
    • @graphql-mesh/utils@0.104.19

0.10.20

Patch Changes

0.10.19

Patch Changes

0.10.18

Patch Changes

  • Updated dependencies [3987b80, 3987b80]:
    • @graphql-mesh/types@0.104.17
    • @graphql-mesh/utils@0.104.17

0.10.17

Patch Changes

  • Updated dependencies [bb42d37, bb42d37]:
    • @graphql-mesh/types@0.104.16
    • @graphql-mesh/utils@0.104.16

0.10.16

Patch Changes

  • Updated dependencies [b077f20]:
    • @graphql-mesh/types@0.104.15
    • @graphql-mesh/utils@0.104.15

0.10.15

Patch Changes

  • Updated dependencies [1db3c6b]:
    • @graphql-mesh/types@0.104.14
    • @graphql-mesh/utils@0.104.14

0.10.14

Patch Changes

0.10.13

Patch Changes

  • Updated dependencies [ffec6e7]:
    • @graphql-mesh/utils@0.104.12
    • @graphql-mesh/types@0.104.12

0.10.12

Patch Changes

  • Updated dependencies [d61faf0]:
    • @graphql-mesh/utils@0.104.11
    • @graphql-mesh/types@0.104.11

0.10.11

Patch Changes

  • Updated dependencies [7852ccd, 7852ccd]:
    • @graphql-mesh/utils@0.104.10
    • @graphql-mesh/types@0.104.10

0.10.10

Patch Changes

  • Updated dependencies [0c18fe1]:
    • @graphql-mesh/types@0.104.9
    • @graphql-mesh/utils@0.104.9

0.10.9

Patch Changes

  • Updated dependencies [fb6e935, fb6e935, fb6e935]:
    • @graphql-mesh/types@0.104.8
    • @graphql-mesh/utils@0.104.8

0.10.8

Patch Changes

  • Updated dependencies [c37c23b]:
    • @graphql-mesh/types@0.104.7
    • @graphql-mesh/utils@0.104.7

0.10.7

Patch Changes

  • Updated dependencies [e2666bc]:
    • @graphql-mesh/utils@0.104.6
    • @graphql-mesh/types@0.104.6

0.10.6

Patch Changes

  • Updated dependencies [9d61d75]:
    • @graphql-mesh/utils@0.104.5
    • @graphql-mesh/types@0.104.5

0.10.5

Patch Changes

  • Updated dependencies [6b4c546]:
    • @graphql-mesh/types@0.104.4
    • @graphql-mesh/utils@0.104.4

0.10.4

Patch Changes

0.10.3

Patch Changes

  • Updated dependencies [1b5d072]:
    • @graphql-mesh/utils@0.104.2
    • @graphql-mesh/types@0.104.2

0.10.2

Patch Changes

  • 1577309 Thanks @ardatan! - Align upstream error extensions to show subgraph correctly in the upstream error extensions

0.10.1

Patch Changes

  • Updated dependencies [b6c083c, f416982]:
    • @graphql-mesh/utils@0.104.1
    • @graphql-mesh/types@0.104.1

0.10.0

Patch Changes

  • Updated dependencies [4528794, 4528794]:
    • @graphql-mesh/utils@0.104.0
    • @graphql-mesh/types@0.104.0

0.9.2

Patch Changes

  • Updated dependencies [903124f]:
    • @graphql-mesh/utils@0.103.21
    • @graphql-mesh/types@0.103.21

0.9.1

Patch Changes

  • Updated dependencies [3f5e0a1]:
    • @graphql-mesh/utils@0.103.20
    • @graphql-mesh/types@0.103.20

0.9.0

Minor Changes

  • #8414 d9cf1d3 Thanks @ardatan! - Auto detection of SOAP version to decide SOAP namespace; For SOAP 1.1, it is set to http://schemas.xmlsoap.org/soap/envelope/ and for SOAP 1.2, it is set to http://www.w3.org/2003/05/soap-envelope.

    If you want to use a custom namespace, you can set it like below;

    import { defineConfig } from '@graphql-mesh/compose-cli'
import { loadSOAPSubgraph } from '@omnigraph/soap'

export const composeConfig = defineConfig({
  subgraphs: [
    {
      sourceHandler: loadSOAPSubgraph('CountryInfo', {
        source:
          'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
        soapNamespace: 'http://foo.com/schemas/soap/envelope'
      })
    }
  ]
})

Patch Changes

  • Updated dependencies [d9cf1d3]:
    • @graphql-mesh/types@0.103.19
    • @graphql-mesh/utils@0.103.19

0.8.18

Patch Changes

0.8.17

Patch Changes

  • Updated dependencies [eee582a]:
    • @graphql-mesh/utils@0.103.17
    • @graphql-mesh/types@0.103.17

0.8.16

Patch Changes

  • Updated dependencies [b44f8b7]:
    • @graphql-mesh/types@0.103.16
    • @graphql-mesh/utils@0.103.16

0.8.15

Patch Changes

  • Updated dependencies [b5c05c4]:
    • @graphql-mesh/types@0.103.15
    • @graphql-mesh/utils@0.103.15

0.8.14

Patch Changes

  • Updated dependencies [fc44a1e]:
    • @graphql-mesh/types@0.103.14
    • @graphql-mesh/utils@0.103.14

0.8.13

Patch Changes

0.8.12

Patch Changes

0.8.11

Patch Changes

  • #8196 3fc1f3e Thanks @ardatan! - - You can now choose the name of the alias you want to use for SOAP body;

    import { defineConfig } from '@graphql-mesh/compose-cli'

export const composeConfig = defineConfig({
  sources: [
    {
      sourceHandler: loadSOAPSubgraph('CountryInfo', {
        source:
          'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
        bodyAlias: 'my-body'
      })
    }
  ]
})
    • Then it will generate a body like below by using the alias;
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:my-body="http://foo.com/">
   <soap:Body>
      <my-body:Foo>
          <my-body:Bar>baz</my-body:Bar>
      </my-body:Foo>
   </soap:Body>
</soap:Envelope>

    If you want to add SOAP headers to the request body like below;

    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:header="http://foo.com/">
   <soap:Header>
      <header:MyHeader>
         <header:UserName>user</header:UserName>
         <header:Password>password</header:Password>
      </header:MyHeader>
   </soap:Header>

    You can add the headers to the configuration like below;

    import { defineConfig } from '@graphql-mesh/compose-cli'
import { loadSOAPSubgraph } from '@omnigraph/soap'

export const composeConfig = defineConfig({
  subgraphs: [
    {
      sourceHandler: loadSOAPSubgraph('CountryInfo', {
        source:
          'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
        soapHeaders: {
          alias: 'header',
          namespace: 'http://foo.com',
          headers: {
            MyHeader: {
              UserName: 'user',
              Password: 'password'
            }
          }
        }
      })
    }
  ]
})

  • Updated dependencies [3fc1f3e, 4011203]:

    • @graphql-mesh/types@0.103.11
    • @graphql-mesh/utils@0.103.11

0.8.10

Patch Changes

  • Updated dependencies [b750a41]:
    • @graphql-mesh/utils@0.103.10
    • @graphql-mesh/types@0.103.10

0.8.9

Patch Changes

  • Updated dependencies [10ba2c4]:
    • @graphql-mesh/utils@0.103.9
    • @graphql-mesh/types@0.103.9

0.8.8

Patch Changes

  • Updated dependencies [93fb364]:
    • @graphql-mesh/utils@0.103.8
    • @graphql-mesh/types@0.103.8

0.8.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.103.7
    • @graphql-mesh/utils@0.103.7

0.8.6

Patch Changes

0.8.5

Patch Changes

  • Updated dependencies [9f9f6fe]:
    • @graphql-mesh/utils@0.103.5
    • @graphql-mesh/types@0.103.5

0.8.4

Patch Changes

  • Updated dependencies [8fcfe3f]:
    • @graphql-mesh/types@0.103.4
    • @graphql-mesh/utils@0.103.4

0.8.3

Patch Changes

  • Updated dependencies [6360755]:
    • @graphql-mesh/utils@0.103.3
    • @graphql-mesh/types@0.103.3

0.8.2

Patch Changes

  • Updated dependencies [bfd8929]:
    • @graphql-mesh/utils@0.103.2
    • @graphql-mesh/types@0.103.2

0.8.1

Patch Changes

0.8.0

Patch Changes

  • Updated dependencies [0e49907, 9873b33]:
    • @graphql-mesh/utils@0.103.0
    • @graphql-mesh/types@0.103.0

0.7.14

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.102.13
    • @graphql-mesh/utils@0.102.13

0.7.13

Patch Changes

0.7.12

Patch Changes

  • Updated dependencies [de41fc2, de41fc2, de41fc2]:
    • @graphql-mesh/transport-common@0.7.12
    • @graphql-mesh/types@0.102.11
    • @graphql-mesh/utils@0.102.11

0.7.11

Patch Changes

  • Updated dependencies [997b81c, 997b81c, 997b81c]:
    • @graphql-mesh/transport-common@0.7.11
    • @graphql-mesh/types@0.102.10
    • @graphql-mesh/utils@0.102.10

0.7.10

Patch Changes

  • Updated dependencies [fad4d27]:
    • @graphql-mesh/utils@0.102.9
    • @graphql-mesh/types@0.102.9
    • @graphql-mesh/transport-common@0.7.10

0.7.9

Patch Changes

  • Updated dependencies [518c42c, 518c42c, 518c42c]:
    • @graphql-mesh/transport-common@0.7.9
    • @graphql-mesh/types@0.102.8
    • @graphql-mesh/utils@0.102.8

0.7.8

Patch Changes

0.7.7

Patch Changes

  • 900e84c Thanks @enisdenjo! - Bump potential CVE dependencies

  • Updated dependencies [bf588d3]:

    • @graphql-mesh/utils@0.102.6
    • @graphql-mesh/types@0.102.6
    • @graphql-mesh/transport-common@0.7.7

0.7.6

Patch Changes

  • Updated dependencies [3bf14b3, b7f6ebf, 0a3e52c]:
    • @graphql-mesh/utils@0.102.5
    • @graphql-mesh/types@0.102.5
    • @graphql-mesh/transport-common@0.7.6

0.7.5

Patch Changes

  • Updated dependencies [5146df0]:
    • @graphql-mesh/transport-common@0.7.5

0.7.4

Patch Changes

  • Updated dependencies [edbc074, edbc074, edbc074]:
    • @graphql-mesh/transport-common@0.7.4
    • @graphql-mesh/types@0.102.4
    • @graphql-mesh/utils@0.102.4

0.7.3

Patch Changes

  • Updated dependencies [14ec31f, 14ec31f, 14ec31f]:
    • @graphql-mesh/transport-common@0.7.3
    • @graphql-mesh/types@0.102.3
    • @graphql-mesh/utils@0.102.3

0.7.2

Patch Changes

  • Updated dependencies [5d95aad]:
    • @graphql-mesh/utils@0.102.2
    • @graphql-mesh/types@0.102.2
    • @graphql-mesh/transport-common@0.7.2

0.7.1

Patch Changes

  • #7013 60bfc22 Thanks @ardatan! - Introduce a standard Upstream Error Format for HTTP-based sources;

    So all sources throw an error will have the extensions in the following format;

    {
  "extensions": {
    "request": {
      // The details of the request made to the upstream service
      "endpoint": "https://api.example.com",
      "method": "GET"
    },
    "response": {
      // The details of the HTTP response from the upstream service
      "status": 401,
      "statusText": "Unauthorized",
      "headers": {
        "content-type": "application/json"
      },
      "body": {
        // The raw body returned by the upstream service
        "error-message": "Unauthorized access"
      }
    }
  }
}

  • Updated dependencies [e49a7e6, 60bfc22]:

    • @graphql-mesh/utils@0.102.1
    • @graphql-mesh/transport-common@0.7.1
    • @graphql-mesh/types@0.102.1

0.7.0

Patch Changes

  • Updated dependencies [13fa835, db41f96]:
    • @graphql-mesh/string-interpolation@0.5.6
    • @graphql-mesh/types@0.102.0
    • @graphql-mesh/utils@0.102.0
    • @graphql-mesh/transport-common@0.7.0

0.6.2

Patch Changes

0.6.1

Patch Changes

  • #7516 67e1062 Thanks @enisdenjo! - Transport’s kind doesn’t need to be typed

  • Updated dependencies [67e1062]:

    • @graphql-mesh/transport-common@0.6.1

0.6.0

Patch Changes

0.5.0

Patch Changes

0.4.7

Patch Changes

  • Updated dependencies [a1bfc49]:
    • @graphql-mesh/types@0.99.7
    • @graphql-mesh/utils@0.99.7
    • @graphql-mesh/transport-common@0.4.7

0.4.6

Patch Changes

0.4.5

Patch Changes

  • Updated dependencies [33c23e8]:
    • @graphql-mesh/utils@0.99.5
    • @graphql-mesh/types@0.99.5
    • @graphql-mesh/transport-common@0.4.5

0.4.4

Patch Changes

  • Updated dependencies [597e790, 597e790]:
    • @graphql-mesh/utils@0.99.4
    • @graphql-mesh/types@0.99.4
    • @graphql-mesh/transport-common@0.4.4

0.4.3

Patch Changes

  • Updated dependencies [5e5dec5, 5e5dec5]:
    • @graphql-mesh/utils@0.99.3
    • @graphql-mesh/types@0.99.3
    • @graphql-mesh/transport-common@0.4.3

0.4.2

Patch Changes

  • Updated dependencies [b01f3ea, 0bdc18d, 4bc495c, 4bc495c, 4bc495c, 345a814]:
    • @graphql-mesh/string-interpolation@0.5.5
    • @graphql-mesh/transport-common@0.4.2
    • @graphql-mesh/types@0.99.2
    • @graphql-mesh/utils@0.99.2

0.4.1

Patch Changes

  • Updated dependencies [7800514, 7800514, 7800514]:
    • @graphql-mesh/transport-common@0.4.1
    • @graphql-mesh/types@0.99.1
    • @graphql-mesh/utils@0.99.1

0.4.0

Patch Changes

0.3.1

Patch Changes

0.3.0

Minor Changes

  • #7145 7544594 Thanks @ardatan! - POTENTIAL BREAKING CHANGE:

    Now @httpOperation and @transport directive serializes headers as [string, string][] instead of stringified JSON.

    @httpOperation(
-  operationSpecificHeaders: [["Authorization", "Bearer 123"], ["X-Api-Key", "123"]]
+  operationSpecificHeaders: "{\"Authorization\": \"Bearer 123\", \"X-Api-Key\": \"123\"}"
)
    @transport(
-  headers: [["Authorization, "Bearer 123"], ["X-Api-Key", "123"]]
+  headers: "{\"Authorization, \"Bearer 123\", \"X-Api-Key\": \"123\"}"
)

    Also incorrect placement of @transport has been fixed to SCHEMA

    directive @transport on
-  FIELD_DEFINITION
+  SCHEMA

    There is still backwards compatibility but this might look like a breaking change for some users during schema validation.

Patch Changes

  • #7145 7544594 Thanks @ardatan! - dependencies updates:

  • #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 @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 @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/ardatan/graphql-mesh/pull/7109

  • Updated dependencies [f985978, 7544594, 7544594]:

    • @graphql-mesh/utils@0.98.9
    • @graphql-mesh/transport-common@0.3.0
    • @graphql-mesh/types@0.98.9

0.2.8

Patch Changes

  • Updated dependencies [4c75671, 88d6232]:
    • @graphql-mesh/types@0.98.8
    • @graphql-mesh/transport-common@0.2.8

0.2.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.98.7
    • @graphql-mesh/transport-common@0.2.7

0.2.6

Patch Changes

0.2.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.98.5
    • @graphql-mesh/transport-common@0.2.5

0.2.4

Patch Changes

  • Updated dependencies [fb59244]:
    • @graphql-mesh/transport-common@0.2.4
    • @graphql-mesh/types@0.98.4

0.2.3

Patch Changes

  • Updated dependencies [c47b2aa]:
    • @graphql-mesh/transport-common@0.2.3
    • @graphql-mesh/types@0.98.3

0.2.2

Patch Changes

  • 96dd11d Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [96dd11d]:

    • @graphql-mesh/transport-common@0.2.2
    • @graphql-mesh/cross-helpers@0.4.2
    • @graphql-mesh/types@0.98.2

0.2.1

Patch Changes

  • Updated dependencies [3d88cb8, 6044b7f]:
    • @graphql-mesh/string-interpolation@0.5.4
    • @graphql-mesh/types@0.98.1
    • @graphql-mesh/transport-common@0.2.1

0.2.0

Patch Changes

  • Updated dependencies [2fcadce, 2fcadce]:
    • @graphql-mesh/transport-common@0.2.0
    • @graphql-mesh/types@0.98.0

0.1.5

Patch Changes

  • Updated dependencies [52f74e7]:
    • @graphql-mesh/types@0.97.5
    • @graphql-mesh/transport-common@0.1.5

0.1.4

Patch Changes

  • Updated dependencies [ff33394]:
    • @graphql-mesh/types@0.97.4
    • @graphql-mesh/transport-common@0.1.4

0.1.3

Patch Changes

  • Updated dependencies [57f4a60]:
    • @graphql-mesh/types@0.97.3
    • @graphql-mesh/transport-common@0.1.3

0.1.2

Patch Changes

  • Updated dependencies [7a712ab]:
    • @graphql-mesh/types@0.97.2
    • @graphql-mesh/transport-common@0.1.2

0.1.1

Patch Changes

  • Updated dependencies [dbaf72c]:
    • @graphql-mesh/types@0.97.1
    • @graphql-mesh/transport-common@0.1.1

0.1.0

Patch Changes

  • Updated dependencies [92dce67]:
    • @graphql-mesh/types@0.97.0
    • @graphql-mesh/transport-common@0.1.0

0.0.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.96.6
    • @graphql-mesh/transport-common@0.0.3

0.0.2

Patch Changes

  • Updated dependencies [4b3ea1d]:
    • @graphql-mesh/types@0.96.5
    • @graphql-mesh/transport-common@0.0.2

0.0.1

Patch Changes