Skip to content

Commit 5dd8233

Browse files
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/[email protected] ### 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/[email protected] ### Patch Changes - Updated dependencies \[[`7cc163ac8`](7cc163a), [`8cbc61406`](8cbc614), [`b694bb1dd`](b694bb1)]: - @apollo/[email protected] Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
1 parent 5e7ead9 commit 5dd8233

File tree

9 files changed

+68
-66
lines changed

9 files changed

+68
-66
lines changed

.changeset/angry-weeks-flash.md

Lines changed: 0 additions & 39 deletions
This file was deleted.

.changeset/good-flies-peel.md

Lines changed: 0 additions & 2 deletions
This file was deleted.

.changeset/kind-yaks-sneeze.md

Lines changed: 0 additions & 13 deletions
This file was deleted.

.changeset/polite-poets-teach.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

package-lock.json

Lines changed: 4 additions & 4 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

packages/integration-testsuite/CHANGELOG.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,12 @@
11
# @apollo/server-integration-testsuite
22

3+
## 4.5.0
4+
5+
### Patch Changes
6+
7+
- 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)]:
8+
- @apollo/server@4.5.0
9+
310
## 4.4.1
411

512
### Patch Changes

packages/integration-testsuite/package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@apollo/server-integration-testsuite",
3-
"version": "4.4.1",
3+
"version": "4.5.0",
44
"description": "Test suite for Apollo Server integrations",
55
"main": "dist/index.js",
66
"types": "dist/index.d.ts",
@@ -28,7 +28,7 @@
2828
"dependencies": {
2929
"@apollo/cache-control-types": "^1.0.2",
3030
"@apollo/client": "^3.6.9",
31-
"@apollo/server": "4.4.1",
31+
"@apollo/server": "4.5.0",
3232
"@apollo/server-plugin-landing-page-graphql-playground": "^4.0.0",
3333
"@apollo/utils.keyvaluecache": "^2.1.0",
3434
"@apollo/utils.createhash": "^2.0.0",

packages/server/CHANGELOG.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,59 @@
11
# @apollo/server
22

3+
## 4.5.0
4+
5+
### Minor Changes
6+
7+
- [#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
8+
9+
Example of all new config options:
10+
11+
```
12+
const server = new ApolloServer({
13+
typeDefs,
14+
resolvers,
15+
plugins: [
16+
process.env.NODE_ENV === 'production'
17+
? ApolloServerPluginLandingPageProductionDefault({
18+
graphRef: 'my-graph-id@my-graph-variant',
19+
collectionId: 'abcdef',
20+
operationId: '12345'
21+
embed: true,
22+
footer: false,
23+
})
24+
: ApolloServerPluginLandingPageLocalDefault({
25+
collectionId: 'abcdef',
26+
operationId: '12345'
27+
embed: {
28+
initialState: {
29+
pollForSchemaUpdates: false,
30+
sharedHeaders: {
31+
"HeaderNeededForIntrospection": "ValueForIntrospection"
32+
},
33+
},
34+
endpointIsEditable: true,
35+
},
36+
footer: false,
37+
}),
38+
],
39+
});
40+
41+
```
42+
43+
- [#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.
44+
45+
### Patch Changes
46+
47+
- [#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.
48+
49+
Who was affected?
50+
51+
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.
52+
53+
How were they affected?
54+
55+
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.
56+
357
## 4.4.1
458

559
### Patch Changes

packages/server/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@apollo/server",
3-
"version": "4.4.1",
3+
"version": "4.5.0",
44
"description": "Core engine for Apollo GraphQL server",
55
"type": "module",
66
"main": "dist/cjs/index.js",

0 commit comments

Comments
 (0)