starred/repo-remover-moollaza
1
0
Fork 0
mirror of https://github.com/moollaza/repo-remover.git synced 2026-04-26 01:05:48 +03:00
Code Issues 6 Projects Releases Packages Wiki Activity

[PR #143] [CLOSED] Bump apollo-server-core from 2.9.14 to 2.16.1 #149

New issue
Closed
opened 2026-02-26 05:30:31 +03:00 by kerem · 0 comments
kerem commented 2026-02-26 05:30:31 +03:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/moollaza/repo-remover/pull/143
Author: @dependabot[bot]
Created: 7/31/2020
Status: ❌ Closed

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

📝 Commits (1)

  • d3b38b4 Bump apollo-server-core from 2.9.14 to 2.16.1

📊 Changes

1 file changed (+455 additions, -186 deletions)

View changed files

📝 yarn.lock (+455 -186)

📄 Description

Bumps apollo-server-core from 2.9.14 to 2.16.1.

Changelog

Sourced from apollo-server-core's changelog.

v2.16.1

  • This release only includes patch updates to dependencies.

v2.16.0

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

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.

v2.14.1

See complete versioning details.

v2.14.0

See complete versioning details.

Commits
  • 128c1b0 Release
  • f4cfb22 Release
  • 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)
  • Additional commits viewable in compare view

Dependabot compatibility score

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

You can disable automated security fix PRs for this repo from the Security Alerts page.

🔄 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/143 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 7/31/2020 **Status:** ❌ Closed **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/apollo-server-core-2.16.1` --- ### 📝 Commits (1) - [`d3b38b4`](https://github.com/moollaza/repo-remover/commit/d3b38b4744b2041a8ea8b87f6f5bfb60d0f0ae1d) Bump apollo-server-core from 2.9.14 to 2.16.1 ### 📊 Changes **1 file changed** (+455 additions, -186 deletions) <details> <summary>View changed files</summary> 📝 `yarn.lock` (+455 -186) </details> ### 📄 Description Bumps [apollo-server-core](https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core) from 2.9.14 to 2.16.1. <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.16.1</h2> <ul> <li>This release only includes patch updates to dependencies.</li> </ul> <h2>v2.16.0</h2> <ul> <li><code>apollo-server-fastify</code>: Pass Fastify's <code>request</code> and <code>reply</code> objects into the <code>context</code> function, which previously had been receiving nothing. [Issue <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/3156">#3156</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/3156">apollographql/apollo-server#3156</a>) [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/3895">#3895</a>(<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/3895">apollographql/apollo-server#3895</a>)</li> <li><code>apollo-server-lamdbda</code>: Automatically decode payloads which are Base64-encoded when the <code>isBase64Encoded</code> boolean is present on Lambda <code>event</code> payloads. [PR <a href="https://github.com/apollographql/apollo-server/tree/HEAD/packages/apollo-server-core/issues/4311">#4311</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4311">apollographql/apollo-server#4311</a>)</li> </ul> <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> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/apollographql/apollo-server/commit/128c1b0930ff789c55ac258a0b579f18c6d5312b"><code>128c1b0</code></a> Release</li> <li><a href="https://github.com/apollographql/apollo-server/commit/f4cfb22b93913c98e54c638ae39f39ed153daf66"><code>f4cfb22</code></a> Release</li> <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>Additional commits viewable in <a href="https://github.com/apollographql/apollo-server/commits/apollo-server-core@2.16.1/packages/apollo-server-core">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=apollo-server-core&package-manager=npm_and_yarn&previous-version=2.9.14&new-version=2.16.1)](https://help.github.com/articles/configuring-automated-security-fixes) 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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/moollaza/repo-remover/network/alerts). </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 05:30:31 +03:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release-please--branches--main--components--repo-remover
v2.0.0
Labels
Clear labels   
bug

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
enhancement
enhancement
good first issue
help wanted
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/repo-remover-moollaza#149
No description provided.