Oliver MxOliver Fairfax, VA They/them pronouns, 27. Full-stack JavaScript developer and Ruby enthusiast. Purveyor of cheesy tech-related animal memes.

MxOliver/DesignIt 2

A Reddit Clone Application with Node.js using postgres, sequelize, and express.

MxOliver/first-contributions 1

🚀✨ Help beginners to contribute to open source projects

MxOliver/Pocket-Therabuddy 1

Mental health web application with mood and habit tracking, coping skill resources, exercises, and a customizable support contact list.

MxOliver/application-api 0

The GraphQL API for the High Fives Application Process

MxOliver/Bloccit-Rails 0

Ruby on Rails Reddit Clone

MxOliver/Budget-App 0

Ruby on Rails personal budget app

MxOliver/Google-Books 0

Simple Google Books API Search application

MxOliver/Learning-Cedar-ArcGis 0

Small exercise using Cedar and ArcGis REST Services

push eventMxOliver/PocketTherabuddy_2.0


commit sha ce58a1b4d5502978000f2f0d26084c1381513d32

Bump apollo-server-core from 2.9.12 to 2.14.2 Bumps [apollo-server-core]( from 2.9.12 to 2.14.2. - [Release notes]( - [Changelog]( - [Commits]( Signed-off-by: dependabot[bot] <>

view details


commit sha 3468b1ee46869c3d72d9393b8669841fdb08ea4f

Merge pull request #7 from MxOliver/dependabot/npm_and_yarn/apollo-server-core-2.14.2 Bump apollo-server-core from 2.9.12 to 2.14.2

view details

push time in 2 months

PR merged MxOliver/PocketTherabuddy_2.0

Bump apollo-server-core from 2.9.12 to 2.14.2 dependencies

Bumps apollo-server-core from 2.9.12 to 2.14.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="">apollo-server-core's changelog</a>.</em></p> <blockquote> <h3>v2.14.2</h3> <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="">Read the full GitHub Security Advisory for details</a></strong>.</li> </ul> <h3>v2.14.1</h3> <blockquote> <p><a href="">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="">#4170</a>](<a href="">apollographql/apollo-server#4170</a>) [PR <a href="">#4175</a>](<a href="">apollographql/apollo-server#4175</a>)</li> </ul> <h3>v2.14.0</h3> <blockquote> <p><a href="">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="">its documentation</a>. For more details, see the attached PR. [PR <a href="">#3988</a>](<a href="">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="">its documentation</a>. [PR <a href="">#4135</a>](<a href="">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 the schema registry in Apollo Graph Manager was to use the CLI and run <code>apollo schema:push</code>. <em>Apollo schema reporting protocol</em> is a <em>new</em> specification for GraphQL servers to automatically report schemas to the Apollo Graph Manager schema registry.</p> <p><strong>To enable schema reporting,</strong> provide a Graph Manager API key (available free from <a href="">Apollo Graph Manager</a>) in the <code>APOLLO_KEY</code> environment variable <em>and</em> set the <code>experimental_schemaReporting</code> option to <code>true</code> in the Apollo Server constructor options, like so:</p> <pre lang="js"><code>const server = new ApolloServer({ typeDefs, resolvers, engine: { experimental_schemaReporting: true, /* Other existing options can remain the same. */ }, }); </code></pre> <blockquote> <p>When enabled, a schema reporter is initiated by the <code>apollo-engine-reporting</code> agent. It will loop until the <code>ApolloServer</code> instance is stopped, periodically calling back to Apollo Graph Manager to send information. The life-cycle of this reporter is managed by the agent.</p> </blockquote> <p>For more details on the implementation of this new protocol, see the PR which introduced it to Apollo Server and the <a href="">preview documentation</a>.</p> </li> </ul> </tr></table> ... (truncated) </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=""><code>a17f26b</code></a> Release</li> <li><a href=""><code>7aaca56</code></a> Update <code>@apollo/gateway</code> and <code>@apollo/federation</code> CHANGELOG before publish.</li> <li><a href=""><code>354d991</code></a> Update for subscription validation rules to Security Advisory.</li> <li><a href=""><code>04fab28</code></a> Merge remote-tracking branch 'origin/master' into advisory-fix-1</li> <li><a href=""><code>02f1fb6</code></a> chore(deps): update dependency gatsby to v2.22.15 (<a href="">#4187</a>)</li> <li><a href=""><code>eadbfc3</code></a> chore(deps): update dependency gatsby to v2.22.13 (<a href="">#4181</a>)</li> <li><a href=""><code>d979a9e</code></a> chore(deps): update dependency @types/lodash to v4.14.154 (<a href="">#4184</a>)</li> <li><a href=""><code>68ff8e5</code></a> chore(deps): update dependency ioredis to v4.17.3 (<a href="">#4182</a>)</li> <li><a href=""><code>00a056a</code></a> chore(deps): update dependency @types/lodash to v4.14.153 (<a href="">#4180</a>)</li> <li><a href=""><code>c0aa7c0</code></a> chore(deps): update dependency @azure/functions to v1.2.2 (<a href="">#4179</a>)</li> <li>Additional commits viewable in <a href="">compare view</a></li> </ul> </details> <br />

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.

<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.


+371 -158

0 comment

1 changed file


pr closed time in 2 months