-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NEBULA-2161: send package version to embeds #7430
NEBULA-2161: send package version to embeds #7430
Conversation
✅ Deploy Preview for apollo-server-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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. |
9866c38
to
5eec097
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one question, otherwise lgtm! Can you add a changeset please?
@trevor-scheer I don't think this is changeset worthy, its not a user facing change at all / no behavior change at all? |
92dcf5f
to
ec62169
Compare
…ut from cdn request logs
…dio deployment logs as a second source
cdefde2
to
a99836f
Compare
packages/server/src/plugin/landingPage/default/getEmbeddedHTML.ts
Outdated
Show resolved
Hide resolved
614e138
to
98986ce
Compare
621557b
to
b2cb19d
Compare
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>
This pr should be rebased off of #7432
Context
JIRA
Slack
What Changed?
This PR does 2 things
How to test
erm, run the landing pages locally, check the console & see that the version shows up correctly in the cdn script url
there are already tests for the html functions