starter.dev
starter.dev copied to clipboard
chore(deps): bump @apollo/server from 4.3.0 to 4.9.3 in /starters/serverless-framework-apollo-contentful
Bumps @apollo/server from 4.3.0 to 4.9.3.
Release notes
Sourced from @apollo/server
's releases.
@apollo/server-integration-testsuite
@4
.9.3Patch Changes
@apollo/server
@4
.9.3Patch Changes
a1c725eaf
Thanks@trevor-scheer
! - Ensure API keys are valid header values on startupApollo Server previously performed no sanitization or validation of API keys on startup. In the case that an API key was provided which contained characters that are invalid as header values, Apollo Server could inadvertently log the API key in cleartext.
This only affected users who:
- Provide an API key with characters that are invalid as header values
- Use either schema or usage reporting
- Use the default fetcher provided by Apollo Server or configure their own
node-fetch
fetcherApollo Server now trims whitespace from API keys and validates that they are valid header values. If an invalid API key is provided, Apollo Server will throw an error on startup.
For more details, see the security advisory: https://github.com/apollographql/apollo-server/security/advisories/GHSA-j5g3-5c8r-7qfx
@apollo/server-integration-testsuite
@4
.9.2Patch Changes
@apollo/server
@4
.9.2Patch Changes
#7699
62e7d940d
Thanks@trevor-scheer
! - Fix error path attachment for list itemsPreviously, when errors occurred while resolving a list item, the trace builder would fail to place the error at the correct path and just default to the root node with a warning message:
Could not find node with path x.y.1, defaulting to put errors on root node.
This change places these errors at their correct paths and removes the log.
@apollo/server-integration-testsuite
@4
.9.1Patch Changes
@apollo/server
@4
.9.1Patch Changes
... (truncated)
Changelog
Sourced from @apollo/server
's changelog.
4.9.3
Patch Changes
a1c725eaf
Thanks@trevor-scheer
! - Ensure API keys are valid header values on startupApollo Server previously performed no sanitization or validation of API keys on startup. In the case that an API key was provided which contained characters that are invalid as header values, Apollo Server could inadvertently log the API key in cleartext.
This only affected users who:
- Provide an API key with characters that are invalid as header values
- Use either schema or usage reporting
- Use the default fetcher provided by Apollo Server or configure their own
node-fetch
fetcherApollo Server now trims whitespace from API keys and validates that they are valid header values. If an invalid API key is provided, Apollo Server will throw an error on startup.
For more details, see the security advisory: https://github.com/apollographql/apollo-server/security/advisories/GHSA-j5g3-5c8r-7qfx
4.9.2
Patch Changes
#7699
62e7d940d
Thanks@trevor-scheer
! - Fix error path attachment for list itemsPreviously, when errors occurred while resolving a list item, the trace builder would fail to place the error at the correct path and just default to the root node with a warning message:
Could not find node with path x.y.1, defaulting to put errors on root node.
This change places these errors at their correct paths and removes the log.
4.9.1
Patch Changes
- #7672
ebfde0007
Thanks@trevor-scheer
! - Add missingnonce
onscript
tag for non-embedded landing page4.9.0
Minor Changes
#7617
4ff81ca50
Thanks@trevor-scheer
! - Introduce newApolloServerPluginSubscriptionCallback
plugin. This plugin implements the subscription callback protocol which is used by Apollo Router. This feature implements subscriptions over HTTP via a callback URL which Apollo Router registers with Apollo Server. This feature is currently in preview and is subject to change.You can enable callback subscriptions like so:
import { ApolloServerPluginSubscriptionCallback } from '@apollo/server/plugin/subscriptionCallback'; import { ApolloServer } from '@apollo/server';
const server = new ApolloServer({
... (truncated)
Commits
a9d288a
Version Packages (#7712)2c8106c
Merge pull request from GHSA-j5g3-5c8r-7qfxd6ce603
create README for technical details of landing pages (#7671)e8c00a7
Version Packages (#7702)62b941a
chore(deps): update all non-major dependencies (#7693)62e7d94
Fix trace placement for errors occurring in lists (#7699)b72485a
chore: update documentation to include install commands for typescript (#7691)a48e8e0
Version Packages (#7673)ebfde00
Add missingnonce
toscript
tag (#7672)1235611
Version Packages (#7661)- 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 show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@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) You can disable automated security fix PRs for this repo from the Security Alerts page.
Deploy Preview for starter-dev canceled.
Name | Link |
---|---|
Latest commit | 65969560198800dba5bceb6964458ca5342eb71a |
Latest deploy log | https://app.netlify.com/sites/starter-dev/deploys/64efb432e831960007841cd5 |
Deploy Preview for shopify-next-tailwind canceled.
Name | Link |
---|---|
Latest commit | 65969560198800dba5bceb6964458ca5342eb71a |
Latest deploy log | https://app.netlify.com/sites/shopify-next-tailwind/deploys/64efb4329eb451000782b971 |
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication