Skip to content

release: on branch next#3379

Open
github-actions[bot] wants to merge 1 commit intonextfrom
changeset-release/next
Open

release: on branch next#3379
github-actions[bot] wants to merge 1 commit intonextfrom
changeset-release/next

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Feb 13, 2026

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

@apollo/gateway@2.14.0

Minor Changes

  • Add opt-out anonymous deployment environment telemetry. To opt-out, set APOLLO_TELEMETRY_DISABLED=1 in your environment. (#3379)

Patch Changes

@apollo/federation-internals@2.14.0

Minor Changes

  • Relax @interfaceObject validation for Fed 1 subgraphs. (#3392)

    Previously, any use of @interfaceObject in a Fed 2 subgraph caused an INTERFACE_OBJECT_USAGE_ERROR if any Fed 1 subgraph was present in the composition, regardless of whether the types conflicted.

    The check is now per-type: an error is only raised when a Fed 2 subgraph uses @interfaceObject on type T and a Fed 1 subgraph has @key on an interface also named T. @key on an interface in a Fed 1 subgraph does not mean it can fulfill the __typename-resolution requirement that @interfaceObject depends on — but they are otherwise compatible with @interfaceObject usage on unrelated types.

Patch Changes

  • Fixed print logic when calculating the max number of elements to include in the message. Previously we were not passing (#3424)
    the current calculated length correctly leading to inclusion of additional elements in the error/hints message.

@apollo/query-graphs@2.14.0

Patch Changes

@apollo/query-planner@2.14.0

Patch Changes

@apollo/subgraph@2.14.0

Patch Changes

apollo-federation-integration-testsuite@2.14.0

Minor Changes

  • Add opt-out anonymous deployment environment telemetry. To opt-out, set APOLLO_TELEMETRY_DISABLED=1 in your environment. (#3379)

Patch Changes

  • Fixed print logic when calculating the max number of elements to include in the message. Previously we were not passing (#3424)
    the current calculated length correctly leading to inclusion of additional elements in the error/hints message.

@github-actions github-actions bot requested a review from a team as a code owner February 13, 2026 21:02
@apollo-librarian
Copy link
Copy Markdown

apollo-librarian bot commented Feb 13, 2026

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: 40cbdc521c84dbcece49430d
Build Logs: View logs


✅ AI Style Review — No Changes Detected

No MDX files were changed in this pull request.

Review Log: View detailed log

This review is AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.

@github-actions github-actions bot force-pushed the changeset-release/next branch from 8127b2b to 4f96382 Compare February 19, 2026 21:01
@codesandbox-ci
Copy link
Copy Markdown

codesandbox-ci bot commented Feb 19, 2026

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.

@github-actions github-actions bot force-pushed the changeset-release/next branch from 4f96382 to 70a7fe4 Compare February 19, 2026 21:30
@github-actions github-actions bot force-pushed the changeset-release/next branch 3 times, most recently from dca4a56 to 8b78236 Compare March 23, 2026 23:03
Copy link
Copy Markdown
Contributor

@sachindshinde sachindshinde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was looking at next, and there's a bug/breaking change in #3391 that means we shouldn't release. I'll file a PR by tonight/early tomorrow with fixes, but I'm filing this review to block for now.

@sachindshinde
Copy link
Copy Markdown
Contributor

Filed the PR with fixes at #3422.

@github-actions github-actions bot force-pushed the changeset-release/next branch from 8b78236 to 9fe00ac Compare March 27, 2026 16:43
@github-actions github-actions bot force-pushed the changeset-release/next branch from 9fe00ac to e258889 Compare April 9, 2026 04:59
@github-actions github-actions bot force-pushed the changeset-release/next branch from e258889 to 573f2bb Compare April 14, 2026 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant