Skip to content

CHANGELOG.md

Latest commit

 

History

History
1144 lines (726 loc) · 59.8 KB

CHANGELOG.md

File metadata and controls

1144 lines (726 loc) · 59.8 KB
Raw

CHANGELOG for @apollo/composition

2.14.4

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.14.4
    • @apollo/query-graphs@2.14.4

2.14.3

Patch Changes

  • Propagate directives from @interfaceObject fields to @external implementations (#3456)

    When an implementation re-declares a field as @external (e.g. to reference it in @requires), the field's only resolvable definition lives on the abstracting @interfaceObject. Directives like @tag applied there were not being propagated to the implementation's copy in the supergraph.

    During add_interface_object_fields, detect implementation fields where every @join__field is external: true and the field is provided by an @interfaceObject, then copy applicable directives onto the implementation field.

  • Updated dependencies []:

    • @apollo/federation-internals@2.14.3
    • @apollo/query-graphs@2.14.3

2.14.2

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.14.2
    • @apollo/query-graphs@2.14.2

2.14.1

Patch Changes

  • Suppress false INCONSISTENT_INTERFACE_VALUE_TYPE_FIELD hints for @interfaceObject (#3444)

    Skip the inconsistent value type field hint when a source is an @interfaceObject (which only contributes specific fields) or when the field is provided by an @interfaceObject in another subgraph (since non-@interfaceObject subgraphs are not expected to define those fields).

  • Updated dependencies [278eb0fc2bc0ef13ba371407df04cfe50fa2887d, 8bb88f9c7b90addd5ef29f9e4a3f9c027e6cf690]:

    • @apollo/federation-internals@2.14.1
    • @apollo/query-graphs@2.14.1

2.14.0

Minor Changes

  • Relax @composeDirective validation when definitions are absent in some subgraphs. (#3422)

    Previously, if some set of spec directives were being composed into the supergraph schema via @composeDirective, then subgraphs with the latest version of that spec would each have to declare all of those spec directive definitions. Not following this rule would often result in composition emitting a DIRECTIVE_COMPOSITION_ERROR error. This restriction has now been relaxed, and a definition needs to only be in at least one of those subgraphs with the latest version of that spec.

    As an example, the following @composeDirective usage could previously fail, but is now valid.

    # subgraph A — composes and defines @foo and @bar
extend schema
  # ...
  @link(url: "https://myorg.dev/myspec/v1.0", import: ["@foo", "@bar"])
  @composeDirective(name: "@foo")
  @composeDirective(name: "@bar")
# ...
directive @foo on FIELD
directive @bar on FIELD

# subgraph B — composes and defines only @foo
extend schema
  # ...
  @link(url: "https://myorg.dev/myspec/v1.0", import: ["@foo"])
  @composeDirective(name: "@foo")
# ...
directive @foo on FIELD

Patch Changes

2.13.3

Patch Changes

  • Mark connect/v0.4 as a preview version so composition does not inject it into the supergraph @link unless a subgraph explicitly uses it. Previously, upgrading to Federation v2.13 would unconditionally stamp connect/v0.4 into the supergraph, causing Router to require the connectors.preview_connect_v0_4 flag even when no subgraph used v0.4 features. (RH-1321) (#3413)

  • Updated dependencies [b5c17ffa73e2de49bd63182a84a7d5837c0ab2d5]:

    • @apollo/federation-internals@2.13.3
    • @apollo/query-graphs@2.13.3

2.13.2

Patch Changes

2.13.1

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.13.1
    • @apollo/query-graphs@2.13.1

2.13.0

Minor Changes

  • Drop Node.js 14/16 support, require Node.js 18+ (#3364)

  • Support ConnectSpec::V0_4 and @link(url: "https://specs.apollo.dev/connect/v0.4") for upcoming connectors release (#3349)

Patch Changes

2.12.2

Patch Changes

2.12.1

Patch Changes

  • Fixed access control verification of transitive requirements (through @requires and/or @fromContext) to ensure it works with chains of transitive dependencies. (#3343)

  • Allow interface object fields to specify access control (#3343)

    Update composition logic to allow specifying access control directives (@authenticated, @requiresScopes and @policy) on @interfaceObject fields. While we disallow access control on interface types and fields, we decided to support it on @interfaceObject as it is a useful pattern to define a single resolver (that may need access controls) for common interface fields. Alternative would require our users to explicitly define resolvers for all implementations which defeats the purpose of @interfaceObject.

    This PR refactors in how we propagate access control by providing additional merge sources when merging directives on interfaces, interface fields and object fields.

  • Updated dependencies [09e596e6a0c753071ca822e84f525d73ada395cf, ac1ed2946c48e0fef4b413b192d8c5fbdb2370ae]:

    • @apollo/federation-internals@2.12.1
    • @apollo/query-graphs@2.12.1

2.12.0

Minor Changes

  • Federation 2.12 and Connect 0.3 (#3276)

  • Added isSuccess argument to @connect and @source (#3294)

  • Fixes a bug where composition may not generate a satisfiability error for an unsatisfiable @shareable mutation field. (#3305) (#3305)

  • Automatically propagate authorization requirements from implementing type to interface in the supergraph. (#3321)

    Authorization requirements now automatically propagate from implementing types to interfaces during composition. Direct auth specifications on interfaces are no longer allowed. Interface access requires satisfying ALL implementing types' requirements (AND rule), with these requirements included in the supergraph for backward compatibility with older routers.

  • Fix transitive auth requirements on @requires and @fromcontext (#3321)

    Adds new postMergeValidation check to ensure that all fields that depends on data from other parts of the supergraph through @requires and/or @fromContext directives explicitly specify matching @authenticated, @requiresScopes and/or @policy auth requirements, e.g.

    type T @key(fields: "id") {
  id: ID!
  extra: String @external
  # we need explicit `@authenticated` as it is needed to access extra
  requiresExtra: String @requires(fields: "extra") @authenticated
}

type T @key(fields: "id") {
  id: ID!
  extra: String @authenticated
}

  • Adding new CompositionOption maxValidationSubgraphPaths. This value represents the maximum number of SubgraphPathInfo objects that may exist in a ValidationTraversal when checking for satisfiability. Setting this value can help composition error before running out of memory. Default is 1,000,000. (#3275)

  • Restrict usage of auth directives on interfaces (#3321)

    Restricts usage of @authenticated, @policy and @requiresScopes from being applied on interfaces, interface objects and their fields.

    GraphQL spec currently does not define any interface inheritance rules and developers have to explicitly redefine all interface fields on their implementations. At runtime, GraphQL servers cannot return abstract types and always return concrete output types. Due to the above, applying auth directives on the interfaces may lead to unexpected runtime behavior as they won't have any effect at runtime.

  • Stricter merge rules for @requiresScopes and @policy (#3321)

    Current merge policies for @authenticated, @requiresScopes and @policy were inconsistent.

    If a shared field uses the same authorization directives across subgraphs, composition merges them using OR logic. However, if a shared field uses different authorization directives across subgraphs composition merges them using AND logic. This simplified schema evolution, but weakened security requirements. Therefore, the behavior has been changed to always apply AND logic to authorization directives applied to the same field across subgraphs.

    Since @policy and @requiresScopes values represent boolean conditions in Disjunctive Normal Form, we can merge them conjunctively to get the final auth requirements. For example:

    # subgraph A
type T @authenticated {
  # requires scopes (A1 AND A2) OR A3
  secret: String @requiresScopes(scopes: [["A1", "A2"], ["A3"]])
}

# subgraph B
type T {
  # requires scopes B1 OR B2
  secret: String @requiresScopes(scopes: [["B1"], ["B2"]]
}

# composed supergraph
type T @authenticated {
  secret: String @requiresScopes(
    scopes: [
      ["A1", "A2", "B1"],
      ["A1", "A2", "B2"],
      ["A3", "B1"],
      ["A3", "B2"]
    ])
}

    This algorithm also deduplicates redundant requirements, e.g.

    # subgraph A
type T {
  # requires A1 AND A2 scopes to access
  secret: String @requiresScopes(scopes: [["A1", "A2"]])
}

# subgraph B
type T {
  # requires only A1 scope to access
  secret: String @requiresScopes(scopes: [["A1"]])
}

# composed supergraph
type T {
  # requires only A1 scope to access as A2 is redundant
  secret: String @requiresScopes(scopes: [["A1"]])
}

  • Fixed handling @requires dependency on fields returned by @interfaceObject (#3318)

    Depending on the merge order of the types, we could fail composition if a type that @requires data from an @interfaceObject is merged before the interface. Updated merge logic to use explicit merge order of scalars, input objects, interfaces, and finally objects.

  • Added preview @cacheTag directive support (#3274)

Patch Changes

2.11.3

Patch Changes

2.11.2

Patch Changes

  • Improve error messages when @composeDirective arguments are NULL or empty strings. (#3283)

    Previous message on undefined/null argument value Cannot read properties of undefined (reading '0')

    New message Argument to @composeDirective in subgraph "${sg.name}" cannot be NULL or an empty String

  • Updated dependencies [28c08bef6e691aefc6ed07c0e7057f9cd803b317]:

    • @apollo/federation-internals@2.11.2
    • @apollo/query-graphs@2.11.2

2.11.1

Patch Changes

  • Adding new CompositionOption maxValidationSubgraphPaths. This value represents the maximum number of SubgraphPathInfo objects that may exist in a ValidationTraversal when checking for satisfiability. Setting this value can help composition error before running out of memory. Default is 1,000,000. (#3254)

  • Fix bug in composition where, when a field's type in a subgraph is a subtype of the field's type in the supergraph, the satisfiability validation spuriously succeeds/errors. (#3277)

  • Updated dependencies [7799ad1717becf15fb0e82f89619f2ec8a24b4d4, b26794c5724ef23d1f0fd45a40aee3d301557489, 51bed5be49d8e87adae59f568315c9e3488a91e0]:

    • @apollo/federation-internals@2.11.1
    • @apollo/query-graphs@2.11.1

2.11.0

Minor Changes

  • Adds connect spec v0.2, available for use with Apollo Router 2.3.0 or greater. (#3262)

Patch Changes

2.11.0-preview.2

Patch Changes

2.11.0-preview.1

Patch Changes

2.11.0-preview.0

Minor Changes

  • Add connect spec v0.2 (#3228)

Patch Changes

2.10.0

Minor Changes

Patch Changes

2.9.3

Patch Changes

2.9.2

Patch Changes

2.9.1

Patch Changes

2.9.0

Minor Changes

  • Implements two new directives for defining custom costs for demand control. The @cost directive allows setting a custom weight to a particular field in the graph, overriding the default cost calculation. The @listSize directive gives the cost calculator information about how to estimate the size of lists returned by subgraphs. This can either be a static size or a value derived from input arguments, such as paging parameters. (#3074)

Patch Changes

2.8.5

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.8.5
    • @apollo/query-graphs@2.8.5

2.8.4

Patch Changes

2.8.3

Patch Changes

2.8.3-beta.2

Patch Changes

2.8.3-beta.1

Patch Changes

  • Fix logic to compute missing subgraphs when generating composition hints/errors (#3076)

  • Updated dependencies []:

    • @apollo/federation-internals@2.8.3-beta.1
    • @apollo/query-graphs@2.8.3-beta.1

2.8.3-beta.0

Patch Changes

2.8.2

Patch Changes

2.8.1

Patch Changes

  • Fix performance regression in needsJoinField() for large graphs (#3038)

  • Updated dependencies []:

    • @apollo/federation-internals@2.8.1
    • @apollo/query-graphs@2.8.1

2.8.0

Minor Changes

  • Implement new directives to allow getting and setting context. This allows resolvers to reference and access data referenced by entities that exist in the GraphPath that was used to access the field. The following example demonstrates the ability to access the prop field within the Child resolver. (#2988)

    type Query {
  p: Parent!
}
type Parent @key(fields: "id") @context(name: "context") {
  id: ID!
  child: Child!
  prop: String!
}
type Child @key(fields: "id") {
  id: ID!
  b: String!
  field(a: String @fromContext(field: "$context { prop }")): Int!
}

Patch Changes

2.8.0-alpha.1

Patch Changes

2.8.0-alpha.0

Minor Changes

  • Implement new directives to allow getting and setting context. This allows resolvers to reference and access data referenced by entities that exist in the GraphPath that was used to access the field. The following example demonstrates the ability to access the prop field within the Child resolver. (#2988)

    type Query {
  p: Parent!
}
type Parent @key(fields: "id") @context(name: "context") {
  id: ID!
  child: Child!
  prop: String!
}
type Child @key(fields: "id") {
  id: ID!
  b: String!
  field(a: String @fromContext(field: "$context { prop }")): Int!
}

Patch Changes

2.7.8

Patch Changes

2.7.7

Patch Changes

  • No logical changes since 2.7.5 or 2.7.6, but we fixed a bug in the release process, so we need to publish a new patch version (2.7.7). (#2999)

  • Updated dependencies [bee0b0828b4fb6a1d3172ac330560e2ab6c046bb]:

    • @apollo/federation-internals@2.7.7
    • @apollo/query-graphs@2.7.7

2.7.6

Patch Changes

  • There is no functionality change between 2.7.5 and 2.7.6. Triggering new release as previous one released partially leading to a broken experience. (#2997)

  • Updated dependencies []:

    • @apollo/federation-internals@2.7.6
    • @apollo/query-graphs@2.7.6

2.7.5

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.7.5
    • @apollo/query-graphs@2.7.5

2.7.4

Patch Changes

2.7.3

Patch Changes

2.7.2

Patch Changes

2.7.1

Patch Changes

2.7.0

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).

  • Support @join__directive(graphs, name, args) directives (#2894)

Patch Changes

2.6.3

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.6.3
    • @apollo/query-graphs@2.6.3

2.6.2

Patch Changes

2.6.1

Patch Changes

  • Updated dependencies [0d5ab01a]:
    • @apollo/federation-internals@2.6.1
    • @apollo/query-graphs@2.6.1

2.6.0

Minor Changes

  • Update license field in package.json to use Elastic-2.0 SPDX identifier (#2741)

  • Introduce the new @policy scope for composition (#2818)

    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 @policy 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 @policy applications from their subgraphs into a supergraph.

    The directive is defined as follows:

    scalar federation__Policy

directive @policy(
  policies: [[federation__Policy!]!]!
) on FIELD_DEFINITION | OBJECT | INTERFACE | SCALAR | ENUM

    The Policy scalar is effectively a String, similar to the FieldSet type.

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

    @link(url: "https://specs.apollo.dev/federation/v2.6", import: [..., "@policy"])

Patch Changes

  • Updated dependencies [b18841be, e325b499]:
    • @apollo/query-graphs@2.6.0
    • @apollo/federation-internals@2.6.0

2.5.7

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.5.7
    • @apollo/query-graphs@2.5.7

2.5.6

Patch Changes

  • Fixing issue where redeclaration of custom scalars in a fed1 schema may cause upgrade errors (#2809)

  • Updated dependencies [c719214a]:

    • @apollo/federation-internals@2.5.6
    • @apollo/query-graphs@2.5.6

2.5.5

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.5.5
    • @apollo/query-graphs@2.5.5

2.5.4

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.5.4
    • @apollo/query-graphs@2.5.4

2.5.3

Patch Changes

  • Modifies the type for the argument of the @requiresScopes from [federation__Scope!]! to [[federation__Scope!]!]!. (#2738)

    The @requiresScopes directives has been pre-emptively introduced in 2.5.0 to support an upcoming Apollo Router feature around scoped accesses. The argument for @requiresScopes in that upcoming feature is changed to accommodate a new semantic. Note that this technically a breaking change to the @requiresScopes directive definition, but as the full feature using that directive has been released yet, this directive cannot effectively be used and this should have no concrete impact.

  • Updated dependencies [4b9a512b, c6e0e76d, 1add932c, 6f1fddb2]:

    • @apollo/federation-internals@2.5.3
    • @apollo/query-graphs@2.5.3

2.5.2

Patch Changes

  • Updated dependencies [35179f08]:
    • @apollo/federation-internals@2.5.2
    • @apollo/query-graphs@2.5.2

2.5.1

Patch Changes

  • Updated dependencies [b9052fdd]:
    • @apollo/federation-internals@2.5.1
    • @apollo/query-graphs@2.5.1

2.5.0

Minor Changes

  • Do not run the full suite of graphQL validations on supergraphs and their extracted subgraphs by default in production environment. (#2657)

    Running those validations on every updates of the schema takes a non-negligible amount of time (especially on large schema) and mainly only serves in catching bugs early in the supergraph handling code, and in some limited cases, provide slightly better messages when a corrupted supergraph is received, neither of which is worth the cost in production environment.

    A new validateSupergraph option is also introduced in the gateway configuration to force this behaviour.

  • Includes an optional Schema Coordinate field in the Composition Hints returned by composition (#2658)

  • For CoreSpecDefintions that opt in, we've added the ability to tie the core spec version to a particular federation version. That means that if there's a new version of, say, the join spec, you won't necessarily get the new version in the supergraph schema if no subgraph requires it. (#2528)

  • 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"])

  • Introduce the new @requiresScopes directive for composition (#2649)

    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 @requiresScopes 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 @requiresScopes applications from their subgraphs into a supergraph. This addition will support a future version of Apollo Router that enables scoped access to specific types and fields via directive applications.

    The directive is defined as follows:

    scalar federation__Scope

directive @requiresScopes(
  scopes: [federation__Scope!]!
) on FIELD_DEFINITION | OBJECT | INTERFACE | SCALAR | ENUM

    The Scope scalar is effectively a String, similar to the FieldSet type.

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

    @link(url: "https://specs.apollo.dev/federation/v2.5", import: [..., "@requiresScopes"])

Patch Changes

2.4.10

Patch Changes

  • Updated dependencies [b6be9f96]:
    • @apollo/federation-internals@2.4.10
    • @apollo/query-graphs@2.4.10

2.4.9

Patch Changes

2.4.8

Patch Changes

2.4.7

Patch Changes

  • Re-work the code use to try to reuse query named fragments to improve performance (thus sometimes improving query (#2604) planning performance), to fix a possibly raised assertion error (with a message of form like Cannot add selection of field X to selection set of parent type Y), and to fix a rare issue where an interface or union field was not being queried for all the types it should be.
  • Updated dependencies [2d44f346]:
    • @apollo/federation-internals@2.4.7
    • @apollo/query-graphs@2.4.7

2.4.6

Patch Changes

  • Updated dependencies [5cd17e69, e136ad87]:
    • @apollo/federation-internals@2.4.6
    • @apollo/query-graphs@2.4.6

2.4.5

Patch Changes

  • Supersedes v2.4.4 due to a publishing error with no dist/ folder (#2583)

  • Updated dependencies [c96e24c4]:

    • @apollo/federation-internals@2.4.5
    • @apollo/query-graphs@2.4.5

2.4.4

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.4.4
    • @apollo/query-graphs@2.4.4

2.4.3

Patch Changes

  • Updated dependencies [f6a8c1ce]:
    • @apollo/federation-internals@2.4.3
    • @apollo/query-graphs@2.4.3

2.4.2

Patch Changes

  • Allow passing print options to the compose method to impact how the supergraph is printed, and adds new printing (#2042) options to order all elements of the schema.
  • Updated dependencies [2c370508, 179b4602]:
    • @apollo/federation-internals@2.4.2
    • @apollo/query-graphs@2.4.2

2.4.1

Patch Changes

  • Start building packages with TS 5.x, which should have no effect on consumers (#2480)

  • Updated dependencies [450b9578, afde3158, eafebc3c, 01fe3f83]:

    • @apollo/query-graphs@2.4.1
    • @apollo/federation-internals@2.4.1

2.4.0

Minor Changes

  • Addition of new query planner node types to enable federated subscriptions support (#2389)

Patch Changes

  • Refactor the internal implementation of selection sets used by the query planner to decrease the code complexity and (#2387) improve query plan generation performance in many cases.

  • Optimises query plan generation for parts of queries that can statically be known to not cross across subgraphs (#2449)

  • Updated dependencies [260c357c, 7bc0f8e8, 1a555d98, cab383b2]:

    • @apollo/federation-internals@2.4.0
    • @apollo/query-graphs@2.4.0

2.4.0-alpha.1

Patch Changes

  • Updated dependencies [7bc0f8e8]:
    • @apollo/federation-internals@2.4.0-alpha.1
    • @apollo/query-graphs@2.4.0-alpha.1

2.4.0-alpha.0

Minor Changes

  • Addition of new query planner node types to enable federated subscriptions support (#2389)

Patch Changes

  • Updated dependencies [6e2d24b5, 1a555d98]:
    • @apollo/federation-internals@2.4.0-alpha.0
    • @apollo/query-graphs@2.4.0-alpha.0

2.3.5

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.3.5
    • @apollo/query-graphs@2.3.5

2.3.4

Patch Changes

  • Updated dependencies [6e2d24b5]:
    • @apollo/federation-internals@2.3.4
    • @apollo/query-graphs@2.3.4

2.3.3

Patch Changes

  • Stop generating misleading "hint" regarding value type fields for interface types that are entity interfaces (they have a @key defined). (#2412)

  • Updated dependencies [de89e504]:

    • @apollo/query-graphs@2.3.3
    • @apollo/federation-internals@2.3.3

2.3.2

Patch Changes

  • Updated dependencies []:
    • @apollo/federation-internals@2.3.2
    • @apollo/query-graphs@2.3.2

2.3.1

Patch Changes

  • Updated dependencies [7e2ca46f]:
    • @apollo/query-graphs@2.3.1
    • @apollo/federation-internals@2.3.1

This CHANGELOG pertains only to Apollo Federation packages in the 2.x range. The Federation v0.x equivalent for this package can be found here on the version-0.x branch of this repo.

2.3.0-beta.2

  • Error on composition when a @shareable field runtime types don't intersect between subgraphs: a @shareable field must resolve the same way in all the subgraphs, but this is impossible if the concrete runtime types have no intersection at all PR #1556.
  • Uses the 0.3 version of the tag spec in the supergraph, which adds @tag directive support for the SCHEMA location PR #2314.
  • Fixes composition issues with @interfaceObject PR #2318.

2.3.0-alpha.0

  • Preserves source of union members and enum values in supergraph PR #2288.
  • BREAKING: composition now rejects @override on interface fields. The @override directive was not meant to be supported on interfaces and was not having any impact whatsoever. If an existing subgraph does have a @override on an interface field, this will now be rejected, but the @override can simply and safely be removed since it previously was ignored.

2.2.0

  • BREAKING: composition now rejects @shareable on interface fields. The @shareable directive is about controlling if multiple subgraphs can resolve a particular field, and as interface field are never directly resolved (it's their implementation that are), having @shareable on interface fields is not completely meaningful and was never meant to be supported. If an existing subgraph does have a @shareable on an interface field, this will now be rejected, but the @shareable can simply and safely be removed since it previously was ignored.
  • Provide support for marking @external on object type PR #2214
  • Drop support for node12 PR #2202
  • Fix error when a skipped enum value had directives applied PR #2232.

2.1.4

  • Improves error message to help with misspelled source of an @override PR #2181.

2.1.2

  • Fix composition of repeatable custom directives PR #2136
  • Allow fields with arguments in @requires PR #2120.

2.1.0

  • Don't apply @shareable when upgrading fed1 supergraphs if it's already @shareable PR #2043
  • Update peer dependency graphql to ^16.5.0 to use GraphQLErrorOptions PR #2060
  • Don't require @link when using @composeDirective PR #2046
  • Add @composeDirective directive to specify directives that should be merged to the supergraph during composition PR #1996.
  • Warn on merging inconsistent non-repeatable directive applications instead of failing composition PR #1840.
  • Expand support for Node.js v18 PR #1884

v2.0.1

  • Use for: SECURITY in the core/link directive application in the supergraph for @inaccessible PR #1715

v2.0.0

  • Previous preview release promoted to general availability! Please see previous changelog entries for full info.

v2.0.0-preview.11

  • Add a level to hints, uppercase their code and related fixes PR #1683.
  • Add support for @inaccessible v0.2 PR #1678

v2.0.0-preview.10

  • Fix merging of Input objects and enum types PR #1672.
  • Fix regression in composition validation introduced by #1653 PR #1673.
  • Add nodes when displaying hints for @override PR #1684

v2.0.0-preview.9

  • Fix handling of core/link when definitions are provided or partially so PR #1662.
  • Optimize composition validation when many entities spans many subgraphs PR #1653.
  • Support for Node 17 PR #1541.
  • Adds Support for @tag/v0.2, which allows the @tag directive to be additionally placed on arguments, scalars, enums, enum values, input objects, and input object fields. PR #1652.
  • Adds support for the @override directive on fields to indicate that a field should be moved from one subgraph to another. PR #1484

v2.0.0-preview.8

NOTE: Be sure to upgrade the gateway before re-composing/deploying with this version. See below and the changelog for @apollo/gateway.

  • Adds support for @inaccessible in subgraphs PR #1638.
  • Fix merging of @tag directive when it is renamed in subgraphs PR #1637.
  • Generates supergraphs with @link instead of @core. As a result, prior federation 2 pre-release gateway will not read supergraphs generated by this version correctly, so you should upgrade the gateway to this version before re-composing/deploying with this version. PR #1628.

v2.0.0-preview.5

  • Fix propagation of @tag to the supergraph and allows @tag to be repeated. Additionally, merged directives (only @tag and @deprecated currently) are not allowed on external fields anymore PR #1592.

v2.0.0-preview.4

  • Released in sync with other federation packages but no changes to this package.

v2.0.0-preview.3

  • Released in sync with other federation packages but no changes to this package.

v2.0.0-preview.2

  • Re-publishing release which published to npm with stale build artifacts from version-0.x release.

v2.0.0-preview.1

  • No-op publish to account for publishing difficulties.

v2.0.0-preview.0

  • Initial "preview" release.

v2.0.0-alpha.6

  • No direct changes, only transitive updates to @apollo/query-graphs and @apollo/federation-internals.

v2.0.0-alpha.5

  • Remove graphql@15 from peer dependencies PR #1472.

v2.0.0-alpha.3

  • Assign and document error codes for all errors PR #1274.

v2.0.0-alpha.2

  • BREAKING: Bump graphql peer dependency to ^15.7.0 PR #1200
  • Add missing dependency to @apollo/query-graphs

v2.0.0-alpha.1

  • 🎉 Initial alpha release of Federation 2.0. For more information, see our documentation. We look forward to your feedback!