release: on branch next

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

Releases

@apollo/composition@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

• Allow known FeatureDefinition subclasses to define custom subgraph schema validation rules (#2910)

• Updated dependencies [6ae42942b13dccd246ccc994faa2cb36cd62cb3c, 66833fb8d04c9376f6ed476fed6b1ca237f477b7, 931f87c6766c7439936df706727cbdc0cd6bcfd8]:

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

@apollo/gateway@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).

Patch Changes

• Updated dependencies [6ae42942b13dccd246ccc994faa2cb36cd62cb3c, 66833fb8d04c9376f6ed476fed6b1ca237f477b7, 931f87c6766c7439936df706727cbdc0cd6bcfd8]:
  • @apollo/query-planner@2.7.0
  • @apollo/composition@2.7.0
  • @apollo/federation-internals@2.7.0

@apollo/federation-internals@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).

• Allow known FeatureDefinition subclasses to define custom subgraph schema validation rules (#2910)

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

@apollo/query-graphs@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).

Patch Changes

• Updated dependencies [6ae42942b13dccd246ccc994faa2cb36cd62cb3c, 66833fb8d04c9376f6ed476fed6b1ca237f477b7, 931f87c6766c7439936df706727cbdc0cd6bcfd8]:
  • @apollo/federation-internals@2.7.0

@apollo/query-planner@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).

Patch Changes

• Updated dependencies [6ae42942b13dccd246ccc994faa2cb36cd62cb3c, 66833fb8d04c9376f6ed476fed6b1ca237f477b7, 931f87c6766c7439936df706727cbdc0cd6bcfd8]:
  • @apollo/query-graphs@2.7.0
  • @apollo/federation-internals@2.7.0

@apollo/subgraph@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).

Patch Changes

• Updated dependencies [6ae42942b13dccd246ccc994faa2cb36cd62cb3c, 66833fb8d04c9376f6ed476fed6b1ca237f477b7, 931f87c6766c7439936df706727cbdc0cd6bcfd8]:
  • @apollo/federation-internals@2.7.0

apollo-federation-integration-testsuite@2.7.0

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.