Version Packages (#7413)

This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 main, this PR will be updated. # Releases ## @apollo/server@4.5.0 ### Minor Changes - [#7431](#7431) [`7cc163ac8`](7cc163a) Thanks [@mayakoneval](https://github.com/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](#7430) [`b694bb1dd`](b694bb1) Thanks [@mayakoneval](https://github.com/mayakoneval)! - We now send your @apollo/server version to the embedded Explorer & Sandbox used in the landing pages for analytics. ### Patch Changes - [#7432](#7432) [`8cbc61406`](8cbc614) Thanks [@mayakoneval](https://github.com/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/server-integration-testsuite@4.5.0 ### Patch Changes - Updated dependencies \[[`7cc163ac8`](7cc163a), [`8cbc61406`](8cbc614), [`b694bb1dd`](b694bb1)]: - @apollo/server@4.5.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
apollographql · Mar 10, 2023 · 5dd8233 · 5dd8233
1 parent 5e7ead9
commit 5dd8233
Show file tree

Hide file tree

Showing 9 changed files with 68 additions and 66 deletions.
diff --git a/.changeset/angry-weeks-flash.md b/.changeset/angry-weeks-flash.md
diff --git a/.changeset/good-flies-peel.md b/.changeset/good-flies-peel.md
diff --git a/.changeset/kind-yaks-sneeze.md b/.changeset/kind-yaks-sneeze.md
diff --git a/.changeset/polite-poets-teach.md b/.changeset/polite-poets-teach.md
diff --git a/package-lock.json b/package-lock.json
diff --git a/packages/integration-testsuite/CHANGELOG.md b/packages/integration-testsuite/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @apollo/server-integration-testsuite
 
+## 4.5.0
+
+### Patch Changes
+
+- Updated dependencies [[`7cc163ac8`](https://github.com/apollographql/apollo-server/commit/7cc163ac88e801324a24ba7d7e11c38796f52bb4), [`8cbc61406`](https://github.com/apollographql/apollo-server/commit/8cbc61406229653454e50ea98f11dbe834e036b5), [`b694bb1dd`](https://github.com/apollographql/apollo-server/commit/b694bb1dd9880f5acee8917de62cdae4ad647c1f)]:
+  - @apollo/server@4.5.0
+
 ## 4.4.1
 
 ### Patch Changes

diff --git a/packages/integration-testsuite/package.json b/packages/integration-testsuite/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@apollo/server-integration-testsuite",
-  "version": "4.4.1",
+  "version": "4.5.0",
   "description": "Test suite for Apollo Server integrations",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -28,7 +28,7 @@
   "dependencies": {
     "@apollo/cache-control-types": "^1.0.2",
     "@apollo/client": "^3.6.9",
-    "@apollo/server": "4.4.1",
+    "@apollo/server": "4.5.0",
     "@apollo/server-plugin-landing-page-graphql-playground": "^4.0.0",
     "@apollo/utils.keyvaluecache": "^2.1.0",
     "@apollo/utils.createhash": "^2.0.0",

diff --git a/packages/server/CHANGELOG.md b/packages/server/CHANGELOG.md
@@ -1,5 +1,59 @@
 # @apollo/server
 
+## 4.5.0
+
+### Minor Changes
+
+- [#7431](https://github.com/apollographql/apollo-server/pull/7431) [`7cc163ac8`](https://github.com/apollographql/apollo-server/commit/7cc163ac88e801324a24ba7d7e11c38796f52bb4) Thanks [@mayakoneval](https://github.com/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](https://github.com/apollographql/apollo-server/pull/7430) [`b694bb1dd`](https://github.com/apollographql/apollo-server/commit/b694bb1dd9880f5acee8917de62cdae4ad647c1f) Thanks [@mayakoneval](https://github.com/mayakoneval)! - We now send your @apollo/server version to the embedded Explorer & Sandbox used in the landing pages for analytics.
+
+### Patch Changes
+
+- [#7432](https://github.com/apollographql/apollo-server/pull/7432) [`8cbc61406`](https://github.com/apollographql/apollo-server/commit/8cbc61406229653454e50ea98f11dbe834e036b5) Thanks [@mayakoneval](https://github.com/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.
+
 ## 4.4.1
 
 ### Patch Changes

diff --git a/packages/server/package.json b/packages/server/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@apollo/server",
-  "version": "4.4.1",
+  "version": "4.5.0",
   "description": "Core engine for Apollo GraphQL server",
   "type": "module",
   "main": "dist/cjs/index.js",