@apollo/[email protected]

Patch Changes

• #7454 f6e3ae021 Thanks @trevor-scheer! - Start building packages with TS 5.x, which should have no effect for users

• Updated dependencies [1e808146a, f6e3ae021, e0db95b96]:

  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• #7439 4668f4594 Thanks @Igloczek! - Export types from response cache plugin

@apollo/[email protected]

Minor Changes

• #7431 7cc163ac8 Thanks @mayakoneval! - In the Apollo Server Landing Page Local config, you can now automatically turn off autopolling on your endpoints as well as pass headers used to introspect your schema, embed an operation from a collection, and configure whether the endpoint input box is editable. In the Apollo Server Landing Page Prod config, you can embed an operation from a collection & we fixed a bug introduced in release 4.4.0

  Example of all new config options:

  const server = new ApolloServer({
    typeDefs,
    resolvers,
    plugins: [
      process.env.NODE_ENV === 'production'
        ? ApolloServerPluginLandingPageProductionDefault({
            graphRef: 'my-graph-id@my-graph-variant',
            collectionId: 'abcdef',
            operationId: '12345'
            embed: true,
            footer: false,
          })
        : ApolloServerPluginLandingPageLocalDefault({
            collectionId: 'abcdef',
            operationId: '12345'
            embed: {
              initialState: {
                pollForSchemaUpdates: false,
                sharedHeaders: {
                  "HeaderNeededForIntrospection": "ValueForIntrospection"
                },
              },
              endpointIsEditable: true,
            },
            footer: false,
          }),
    ],
  });
  
  

• #7430 b694bb1dd Thanks @mayakoneval! - We now send your @apollo/server version to the embedded Explorer & Sandbox used in the landing pages for analytics.

Patch Changes

• #7432 8cbc61406 Thanks @mayakoneval! - Bug fix: TL;DR revert a previous change that stops passing includeCookies from the prod landing page config.

  Who was affected?

  Any Apollo Server instance that passes a graphRef to a production landing page with a non-default includeCookies value that does not match the Include cookies setting on your registered variant on studio.apollographql.com.

  How were they affected?

  From release 4.4.0 to this patch release, folks affected would have seen their Explorer requests being sent with cookies included only if they had set Include cookies on their variant. Cookies would not have been included by default.

@apollo/[email protected]

Patch Changes

• Updated dependencies [7cc163ac8, 8cbc61406, b694bb1dd]:
  • @apollo/[email protected]

@apollo/[email protected]

Minor Changes

• #7411 021460e95 Thanks @trevor-scheer! - Update protobuf which includes updates for supporting (notably) ConditionNode in the gateway

@apollo/[email protected]

Patch Changes

• Updated dependencies [021460e95]:
  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• #7381 29038a4d3 Thanks @renovate! - Update graphql-http dependency

• Updated dependencies [021460e95]:

  • @apollo/[email protected]
  • @apollo/[email protected]

@apollo/[email protected]

Minor Changes

• #7358 f2d433b4f Thanks @esilverm! - Show "Include Cookies" toggle in Embedded Sandbox landing page.

@apollo/[email protected]

Patch Changes

• Updated dependencies [f2d433b4f]:
  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• #7331 9de18b34c Thanks @trevor-scheer! - Unpin node-abort-controller and update to latest unbreaking patch

• #7136 8c635d104 Thanks @trevor-scheer! - Errors reported by subgraphs (with no trace data in the response) are now accurately reflected in the numeric error stats.

  Operations that receive errors from subgraphs (with no trace data in the response) are no longer sent as incomplete, error-less traces.

  Note: in order for this fix to take effect, your @apollo/gateway version must be updated to v2.3.1 or later.