adex-platform
adex-platform copied to clipboard
Bump apollo-server from 2.24.1 to 2.26.1
Bumps apollo-server from 2.24.1 to 2.26.1.
Changelog
Sourced from apollo-server's changelog.
v2.26.1
- Update fork of
graphql-uploadto a version that specifies its dependency on@types/fs-capacitormore precisely to fix a build breakage. [Issue #7060](apollographql/apollo-server#7060)v2.26.0
- Backport [PR #5537](apollographql/apollo-server#5537) from Apollo Server 3. This fixes a TypeScript declaration relating to the Fetch API. We believe this will make it possible to use Apollo Server 2 with Apollo Gateway 0.52.0. (This change does not provide any functionality other than hopefully fixing some TypeScript builds, so if it turns out that this breaks your TypeScript build instead, just don't take the upgrade. We encourage you to upgrade to actively supported Apollo major versions instead.) [PR #6829](apollographql/apollo-server#6829)
v2.25.4
- ⚠️ SECURITY: If your server does not explicitly enable
graphql-uploadsupport via theuploadsoption tonew ApolloServerand your schema does not use theUploadscalar (other than in its own definition), Apollo Server will not process themultipart/form-datarequests sent bygraphql-uploadclients. This fixes a Cross-Site Request Forgery (CSRF) vulnerability where origins could cause browsers to execute mutations using a user's cookies even when those origins are not allowed by your CORS policy. If you do use uploads in your server, the vulnerability still exists with this version; you should instead upgrade to Apollo Server v3.7 and enable the CSRF prevention feature. (The AS3.7 CSRF prevention feature also protects against other forms of CSRF such as timing attacks against read-only query operations.) See advisory GHSA-2p3c-p3qw-69r4 for more details.v2.25.3
- ⚠️ SECURITY
apollo-server-core: Update default version of the GraphQL Playground React app loaded from the CDN to be@apollographql/[email protected]. This patches an XSS vulnerability. Note that if you are pinning the Playground React app version in your app withnew ApolloServer({playground: {version: 'some version'}}), you will need to update the specified version to 1.7.42 or later to avoid this vulnerability. If you disable GraphQL Playground withnew ApolloServer({playground: false}), this vulnerability does not affect you. See advisory GHSA-qm7x-rc44-rrqw for more details.v2.25.2
apollo-server-express: Update dependencies on@types/expressand@types/express-serve-static-core. [PR #5352](apollographql/apollo-server#5352)v2.25.1
apollo-server-core,apollo-server-express: Upgradesubscriptions-transport-wsdependency and remove unneeded runtime dependency onws. This should enable you to install Apollo Server without depending on versions ofwsvulnerable to CVE-2021-32640. Note that the superficial integration of the unmaintainedsubscriptions-transport-wspackage will be removed in Apollo Server 3; you can also avoid this vulnerability by disabling the built-in subscription support withnew ApolloServer({subscriptions: false})and using a maintained package such asgraphql-wsinstead. (Instead of taking this upgrade, you can also upgradewsto5.2.3, which was just released.)v2.25.0
apollo-server-core: You may now specify your Studio graph as a graph ref (id@variant) via theAPOLLO_GRAPH_REFenvironment variable ornew ApolloServer({apollo: {graphRef}})instead of specifying graph ID and graph variant separately. Theapolloobject passed to pluginserverWillStartand to gatewayloadnow contains agraphReffield.apollo-server-core: Fix a race condition where schema reporting could lead to a delay at process shutdown. [PR #5222](apollographql/apollo-server#5222)apollo-server-core: Allow the Fetch API implementation to be overridden for the schema reporting and usage reporting plugins via a newfetcheroption. [PR #5179](apollographql/apollo-server#5179)apollo-server-core: Theserver.executeOperationmethod (designed for testing) can now take itsqueryas aDocumentNode(eg, agql-tagged string) in addition to as a string. (This matches the behavior of theapollo-server-testingcreateTestClientfunction which is now deprecated.) We now recommend this method instead ofapollo-server-testingin our docs. [Issue #4952](apollographql/apollo-server#4952)apollo-server-testing: Replace README with a deprecation notice explaining how to useserver.executeOperationinstead. [Issue #4952](apollographql/apollo-server#4952)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.