[PR #133] [MERGED] [Security] Bump apollo-server-core from 2.9.14 to 2.15.1 #138

New issue

Closed

opened 2026-02-26 05:30:30 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 05:30:30 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/moollaza/repo-remover/pull/133
Author: @dependabot-preview[bot]
Created: 7/1/2020
Status: ✅ Merged
Merged: 7/31/2020
Merged by: @moollaza

Base: master ← Head: dependabot/npm_and_yarn/apollo-server-core-2.15.1

📝 Commits (1)

f1b1e8f [Security] Bump apollo-server-core from 2.9.14 to 2.15.1

📊 Changes

1 file changed (+452 additions, -183 deletions)

View changed files

📝 yarn.lock (+452 -183)

📄 Description

Bumps apollo-server-core from 2.9.14 to 2.15.1. This update includes a security fix.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Introspection in schema validation in Apollo Server We encourage all users of Apollo Server to read this advisory in its entirety to understand the impact. The Resolution section contains details on patched versions.

Impact

If subscriptions: false is passed to the ApolloServer constructor options, there is no impact. If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport and are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable. If introspection: true is passed to the ApolloServer constructor options, the impact is limited to user-provided validation rules (i.e., using validationRules) since there would be no expectation that introspection was disabled.

The enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory. Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by this advisory.

> Note: Unless subscriptions: false is explicitly passed to the constructor parameters of new ApolloServer({ ... }), subscriptions are enabled by default, whether or not there is a Subscription type present in the schema. As an alternative to upgrading to a patched version, see the Workarounds section below to disable subscriptions if it is not necessary.

In cases where subscriptions: false is not explicitly set, the subscription server is impacted since validation rules which are enforced on the main request pipeline within Apollo Server were not being passed to the SubscriptionServer.create invocation (seen here, prior to the patch).

The omitted validation rules for the subscription server include any validationRules passed by implementors to the ApolloServer constructor which were expected to be enforced on the subscriptions WebSocket endpoint. Additionally, because an internal NoIntrospection validation rule is used to disable introspection, it would have been possible to introspect a server on the WebSocket endpoint that the SubscriptionServer creates even though it was not possible on other transports (e.g. HTTP).

The severity of risk depends on whether sensitive information is being stored in the schema itself. The contents of schema descriptions, or secrets which might be revealed by the names of types or field names within those types, will determine the risk to individual implementors.

Affected packages

The bug existed in apollo-server-core versions prior to version 2.14.2, however, this means all integration packages (e.g., apollo-server-express, etc.) prior to version 2.14.2 which depend on apollo-server-core for their subscriptions support are affected. This includes the apollo-server package that automatically provides an Express server.

Affected versions: < 2.14.2

Changelog

Sourced from apollo-server-core's changelog.

v2.15.1

The default branch of the repository has been changed to main. As this changed a number of references in the repository's package.json and README.md files (e.g., for badges, links, etc.), this necessitates a release to publish those changes to npm. [PR #4302](apollographql/apollo-server#4302)

v2.15.0

apollo-engine-reporting: Added a reportTiming API to allow trace reporting to be enabled or disabled on a per request basis. The option takes either a boolean or a predicate function that takes a GraphQLRequestContextDidResolveOperation or GraphQLRequestContextDidEncounterErrors and returns a boolean. If the boolean is false the request will not be instrumented for tracing and no trace will be sent to Apollo Graph Manager. The default is true so all traces will get instrumented and sent, which is the same as the previous default behavior. [PR #3918](apollographql/apollo-server#3918)

apollo-engine-reporting: Removed GraphQLServerOptions.reporting. It isn't known whether a trace will be reported at the beginning of the request because of the above change. We believe this field was only used internally within Apollo Server; let us know if this is a problem and we can suggest alternatives. Additionally, the field requestContext.metrics.captureTraces is now initialized later in the request pipeline. [PR #3918](apollographql/apollo-server#3918)

apollo-engine-reporting: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. [PR #4246](apollographql/apollo-server#4246)

apollo-engine-reporting: Remove the experimental_ prefix from schema reporting options, and specifically rename experimental_schemaReporting option name to reportSchema. (The old option names remain functional, but are deprecated.) [PR #4236](apollographql/apollo-server#4236)

v2.14.5

apollo-engine-reporting: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. [PR #4246](apollographql/apollo-server#4246)

v2.14.4

apollo-engine-reporting: Add environment variable APOLLO_SCHEMA_REPORTING that can enable schema reporting. If experimental__schemaReporting is set it will override the environment variable. [PR #4206](apollographql/apollo-server#4206)

apollo-engine-reporting: The schema reporting URL has been changed to use the new dedicated sub-domain https://edge-server-reporting.api.apollographql.com. [PR #4232](apollographql/apollo-server#4232)

apollo-server-core: Though Apollo Server is not affected due to the way it is integrated, in response to an upstream security advisory for GraphQL Playground we have published the same patch on our @apollographql/graphql-playground-html fork and bumped Apollo Server to use it. Again, this was done out of an abundance of caution since the way that Apollo Server utilizes renderPlaygroundPage is not vulnerable as it does not allow per-request Playground configuration that could allow interpolation of user-input. [PR #4231](apollographql/apollo-server#4231)

v2.14.3

This release only includes patch updates to dependencies.

v2.14.2

Note: This release is is related to a GitHub Security Advisory published by the Apollo Server team. Please read the attached advisory to understand the impact.

⚠️ SECURITY: Pass all schema validation rules to the subscription server, including validation rules that restrict introspection when introspection is meant to be disabled. Read the full GitHub Security Advisory for details.

v2.14.1

See complete versioning details.

apollo-server-testing: Ensure that user-provided context is cloned when using createTestClient, per the instructions in the intergration testing section of the Apollo Server documentation. [Issue #4170](apollographql/apollo-server#4170) [PR #4175](apollographql/apollo-server#4175)

v2.14.0

See complete versioning details.

apollo-server-core / apollo-server-plugin-base: Add support for willResolveField and corresponding end-handler within executionDidStart. This brings the remaining bit of functionality that was previously only available from graphql-extensions to the new plugin API. The graphql-extensions API (which was never documented) will be deprecated in Apollo Server 3.x. To see the documentation for the request pipeline API, see its documentation. For more details, see the attached PR. [PR #3988](apollographql/apollo-server#3988)

apollo-server-core: Deprecate graphql-extensions. All internal usages of the graphql-extensions API have been migrated to the request pipeline plugin API. For any implementor-supplied extensions, a deprecation warning will be printed once per-extension, per-server-startup, notifying of the intention to deprecate. Extensions should migrate to the plugin API, which is outlined in its documentation. [PR #4135](apollographql/apollo-server#4135)

apollo-engine-reporting: Currently only for non-federated graphs. Added an experimental schema reporting option, experimental_schemaReporting, for Apollo Graph Manager users. During this experiment, we'd appreciate testing and feedback from current and new users of the schema registry!

Prior to the introduction of this feature, the only way to get schemas into

Commits

8cfc947 Release
9c5a3c8 Align all of this repository's package.json's author declarations.
0aef210 Update package.json files to specify directory within repository.
c6ea883 Update URLs to use new default branch name (i.e., main).
6f7bdc6 Release
803db44 Release
a7d6e26 Release
54ff1e6 feat(reporting): Add reportTiming option to EngineReportingOptions (#3918)
e527472 Check the agent's schemaReport field instead of checking options
a9c4b3d Throw if schema-reporting is enabled for either the gateway or for federated ...
Additional commits viewable in compare view

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 rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will 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 version will 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 dependency will 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 labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
@dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

Update frequency (including time of day and day of week)
Pull request limits (per update run and/or open at any time)
Out-of-range updates (receive only lockfile updates, if desired)
Security updates (receive only security updates, if desired)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/moollaza/repo-remover/pull/133 **Author:** [@dependabot-preview[bot]](https://github.com/apps/dependabot-preview) **Created:** 7/1/2020 **Status:** ✅ Merged **Merged:** 7/31/2020 **Merged by:** [@moollaza](https://github.com/moollaza) **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/apollo-server-core-2.15.1` --- ### 📝 Commits (1) - [`f1b1e8f`](https://github.com/moollaza/repo-remover/commit/f1b1e8f0fbaacbbcca1913557bcfacd1b8880587) [Security] Bump apollo-server-core from 2.9.14 to 2.15.1 ### 📊 Changes **1 file changed** (+452 additions, -183 deletions) <details> <summary>View changed files</summary> 📝 `yarn.lock` (+452 -183) </details> ### 📄 Description Bumps [apollo-server-core](https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core) from 2.9.14 to 2.15.1. **This update includes a security fix.** <details> <summary>Vulnerabilities fixed</summary> <p><em>Sourced from <a href="https://github.com/advisories/GHSA-w42g-7vfc-xf37">The GitHub Security Advisory Database</a>.</em></p> <blockquote> <p><strong>Introspection in schema validation in Apollo Server</strong> We encourage all users of Apollo Server to read this advisory in its entirety to understand the impact. The <em>Resolution</em> section contains details on patched versions.</p> <h3>Impact</h3> <p>If <code>subscriptions: false</code> is passed to the <code>ApolloServer</code> constructor options, there is no impact. If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport <strong>and</strong> are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable. If <code>introspection: true</code> is passed to the <code>ApolloServer</code> constructor options, the impact is limited to user-provided validation rules (i.e., using <code>validationRules</code>) since there would be no expectation that introspection was disabled.</p> <p>The enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory. Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by this advisory.</p> <p>> <strong>Note:</strong> Unless <code>subscriptions: false</code> is explicitly passed to the constructor parameters of <code>new ApolloServer({ ... })</code>, <strong>subscriptions are enabled by default, whether or not there is a <code>Subscription</code> type present in the schema.</strong> As an alternative to upgrading to a patched version, see the <em>Workarounds</em> section below to disable subscriptions if it is not necessary.</p> <p>In cases where <code>subscriptions: false</code> is <strong>not</strong> explicitly set, the subscription server <strong>is impacted</strong> since validation rules which are enforced on the main request pipeline within Apollo Server were not being passed to the <code>SubscriptionServer.create</code> invocation (<a href="https://github.com/apollographql/apollo-server/blob/7d6f23443e52a90deb74f152f34bb76eea78ee19/packages/apollo-server-core/src/ApolloServer.ts#L677-L726">seen here, prior to the patch</a>).</p> <p>The omitted validation rules for the subscription server include any <code>validationRules</code> passed by implementors to the <code>ApolloServer</code> constructor which were expected to be enforced on the subscriptions WebSocket endpoint. <strong>Additionally</strong>, because an internal <a href="https://github.com/apollographql/apollo-server/blob/7d6f23443/packages/apollo-server-core/src/ApolloServer.ts#L77-L88"><code>NoIntrospection</code></a> validation rule is used to disable introspection, it would have been possible to introspect a server on the WebSocket endpoint that the <code>SubscriptionServer</code> creates even though it was not possible on other transports (e.g. HTTP).</p> <p><strong>The severity of risk depends on whether sensitive information is being stored in the schema itself.</strong> The contents of schema descriptions, or secrets which might be revealed by the names of types or field names within those types, will determine the risk to individual implementors.</p> <h3>Affected packages</h3> <p>The bug existed in <code>apollo-server-core</code> versions prior to version 2.14.2, however, this means all integration packages (e.g., <code>apollo-server-express</code>, etc.) prior to version 2.14.2 which depend on <code>apollo-server-core</code> for their subscriptions support are affected. This includes the <code>apollo-server</code> package that automatically provides an Express server.</p>  <p>Affected versions: < 2.14.2</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/apollographql/apollo-server/blob/main/CHANGELOG.md">apollo-server-core's changelog</a>.</em></p> <blockquote> <h2>v2.15.1</h2> <ul> <li>The default branch of the repository has been changed to <code>main</code>. As this changed a number of references in the repository's <code>package.json</code> and <code>README.md</code> files (e.g., for badges, links, etc.), this necessitates a release to publish those changes to npm. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4302">#4302</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4302">apollographql/apollo-server#4302</a>)</li> </ul> <h2>v2.15.0</h2> <ul> <li><code>apollo-engine-reporting</code>: Added a <code>reportTiming</code> API to allow trace reporting to be enabled or disabled on a per request basis. The option takes either a boolean or a predicate function that takes a <a href="https://github.com/apollographql/apollo-server/blob/a926b7eedbb87abab2ec70fb03d71743985cb18d/packages/apollo-server-types/src/index.ts#L185-L190"><code>GraphQLRequestContextDidResolveOperation</code></a> or <a href="https://github.com/apollographql/apollo-server/blob/a926b7eedbb87abab2ec70fb03d71743985cb18d/packages/apollo-server-types/src/index.ts#L191-L195"><code>GraphQLRequestContextDidEncounterErrors</code></a> and returns a boolean. If the boolean is false the request will not be instrumented for tracing and no trace will be sent to Apollo Graph Manager. The default is <code>true</code> so all traces will get instrumented and sent, which is the same as the previous default behavior. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/3918">#3918</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/3918">apollographql/apollo-server#3918</a>)</li> <li><code>apollo-engine-reporting</code>: Removed <code>GraphQLServerOptions.reporting</code>. It isn't known whether a trace will be reported at the beginning of the request because of the above change. We believe this field was only used internally within Apollo Server; let us know if this is a problem and we can suggest alternatives. Additionally, the field <code>requestContext.metrics.captureTraces</code> is now initialized later in the request pipeline. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/3918">#3918</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/3918">apollographql/apollo-server#3918</a>)</li> <li><code>apollo-engine-reporting</code>: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4246">#4246</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4246">apollographql/apollo-server#4246</a>)</li> <li><code>apollo-engine-reporting</code>: Remove the <code>experimental_</code> prefix from schema reporting options, and specifically rename <code>experimental_schemaReporting</code> option name to <code>reportSchema</code>. (The old option names remain functional, but are deprecated.) [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4236">#4236</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4236">apollographql/apollo-server#4236</a>)</li> </ul> <h2>v2.14.5</h2> <ul> <li><code>apollo-engine-reporting</code>: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4246">#4246</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4246">apollographql/apollo-server#4246</a>)</li> </ul> <h2>v2.14.4</h2> <ul> <li><code>apollo-engine-reporting</code>: Add environment variable <code>APOLLO_SCHEMA_REPORTING</code> that can enable schema reporting. If <code>experimental__schemaReporting</code> is set it will override the environment variable. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4206">#4206</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4206">apollographql/apollo-server#4206</a>)</li> <li><code>apollo-engine-reporting</code>: The schema reporting URL has been changed to use the new dedicated sub-domain <code>https://edge-server-reporting.api.apollographql.com</code>. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4232">#4232</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4232">apollographql/apollo-server#4232</a>)</li> <li><code>apollo-server-core</code>: Though Apollo Server <strong>is not affected</strong> due to the way it is integrated, in response to <a href="https://github.com/prisma-labs/graphql-playground/security/advisories/GHSA-4852-vrh7-28rf">an upstream security advisory for GraphQL Playground</a> we have published <a href="https://github.com/prisma-labs/graphql-playground/commit/bf1883db538c97b076801a60677733816cb3cfb7">the same patch</a> on our <code>@apollographql/graphql-playground-html</code> fork and bumped Apollo Server to use it. Again, this was done out of an <strong>abundance of caution</strong> since the way that Apollo Server utilizes <code>renderPlaygroundPage</code> is <em>not</em> vulnerable as it does not allow per-request Playground configuration that could allow interpolation of user-input. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4231">#4231</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4231">apollographql/apollo-server#4231</a>)</li> </ul> <h2>v2.14.3</h2> <ul> <li>This release only includes patch updates to dependencies.</li> </ul> <h2>v2.14.2</h2> <blockquote> <p><strong>Note:</strong> This release is is related to a GitHub Security Advisory published by the Apollo Server team. Please read the attached advisory to understand the impact.</p> </blockquote> <ul> <li>⚠️ <strong>SECURITY:</strong> Pass all schema validation rules to the subscription server, including validation rules that restrict introspection when introspection is meant to be disabled. <strong><a href="https://github.com/apollographql/apollo-server/security/advisories/GHSA-w42g-7vfc-xf37">Read the full GitHub Security Advisory for details</a></strong>.</li> </ul> <h2>v2.14.1</h2> <blockquote> <p><a href="https://github.com/apollographql/apollo-server/commit/2da65ef9204027e43baedf9ce385bb3794fd0c9b">See complete versioning details.</a></p> </blockquote> <ul> <li><code>apollo-server-testing</code>: Ensure that user-provided context is cloned when using <code>createTestClient</code>, per the instructions in the <a href="">intergration testing</a> section of the Apollo Server documentation. [Issue <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4170">#4170</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4170">apollographql/apollo-server#4170</a>) [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4175">#4175</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4175">apollographql/apollo-server#4175</a>)</li> </ul> <h2>v2.14.0</h2> <blockquote> <p><a href="https://github.com/apollographql/apollo-server/commit/d159e320879f594ba2d04036e3e1aa0653ff164d">See complete versioning details.</a></p> </blockquote> <ul> <li> <p><code>apollo-server-core</code> / <code>apollo-server-plugin-base</code>: Add support for <code>willResolveField</code> and corresponding end-handler within <code>executionDidStart</code>. This brings the remaining bit of functionality that was previously only available from <code>graphql-extensions</code> to the new plugin API. The <code>graphql-extensions</code> API (which was never documented) will be deprecated in Apollo Server 3.x. To see the documentation for the request pipeline API, see <a href="https://www.apollographql.com/docs/apollo-server/integrations/plugins/">its documentation</a>. For more details, see the attached PR. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/3988">#3988</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/3988">apollographql/apollo-server#3988</a>)</p> </li> <li> <p><code>apollo-server-core</code>: Deprecate <code>graphql-extensions</code>. All internal usages of the <code>graphql-extensions</code> API have been migrated to the request pipeline plugin API. For any implementor-supplied <code>extensions</code>, a deprecation warning will be printed once per-extension, per-server-startup, notifying of the intention to deprecate. Extensions should migrate to the plugin API, which is outlined in <a href="https://www.apollographql.com/docs/apollo-server/integrations/plugins/">its documentation</a>. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4135">#4135</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4135">apollographql/apollo-server#4135</a>)</p> </li> <li> <p><code>apollo-engine-reporting</code>: <strong>Currently only for non-federated graphs.</strong> Added an <em>experimental</em> schema reporting option, <code>experimental_schemaReporting</code>, for Apollo Graph Manager users. <strong>During this experiment, we'd appreciate testing and feedback from current and new users of the schema registry!</strong></p> <p>Prior to the introduction of this feature, the only way to get schemas into</p> </li> </ul>  </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/apollographql/apollo-server/commit/8cfc947ed56fa3f32b82b32b4bcca53470712984"><code>8cfc947</code></a> Release</li> <li><a href="https://github.com/apollographql/apollo-server/commit/9c5a3c8cbd3b694b571d5919b235ebfd31916066"><code>9c5a3c8</code></a> Align all of this repository's <code>package.json</code>'s <code>author</code> declarations.</li> <li><a href="https://github.com/apollographql/apollo-server/commit/0aef210bdc017879376064667787da83a8a32dca"><code>0aef210</code></a> Update <code>package.json</code> files to specify <code>directory</code> within <code>repository</code>.</li> <li><a href="https://github.com/apollographql/apollo-server/commit/c6ea883d1ff40601b512a6de25c6f36be12e1688"><code>c6ea883</code></a> Update URLs to use new default branch name (i.e., <code>main</code>).</li> <li><a href="https://github.com/apollographql/apollo-server/commit/6f7bdc6099669728926ea88f6317cb17cc6a4b43"><code>6f7bdc6</code></a> Release</li> <li><a href="https://github.com/apollographql/apollo-server/commit/803db445585364f1ad75b1984008ce44524679c6"><code>803db44</code></a> Release</li> <li><a href="https://github.com/apollographql/apollo-server/commit/a7d6e26cb1915a2d11f766df84d555562e9986ba"><code>a7d6e26</code></a> Release</li> <li><a href="https://github.com/apollographql/apollo-server/commit/54ff1e68b62f9fbdc366f48562caf531cadf6abb"><code>54ff1e6</code></a> feat(reporting): Add <code>reportTiming</code> option to <code>EngineReportingOptions</code> (<a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/3918">#3918</a>)</li> <li><a href="https://github.com/apollographql/apollo-server/commit/e5274728f6976e49ac892ea2e4690fa269ec162f"><code>e527472</code></a> Check the agent's schemaReport field instead of checking options</li> <li><a href="https://github.com/apollographql/apollo-server/commit/a9c4b3d0ccff552979927fdac333977b7e1001c3"><code>a9c4b3d</code></a> Throw if schema-reporting is enabled for either the gateway or for federated ...</li> <li>Additional commits viewable in <a href="https://github.com/apollographql/apollo-server/commits/apollo-server-core@2.15.1/packages/apollo-server-core">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=apollo-server-core&package-manager=npm_and_yarn&previous-version=2.9.14&new-version=2.15.1)](https://dependabot.com/compatibility-score/?dependency-name=apollo-server-core&package-manager=npm_and_yarn&previous-version=2.9.14&new-version=2.15.1) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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 labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>