Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update apollo graphql packages #1452

Merged
merged 1 commit into from
Apr 12, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/federation 0.22.0 -> 0.23.0 age adoption passing confidence
@apollo/gateway ^0.24.4 -> ^0.26.0 age adoption passing confidence
apollo-server-express 2.21.2 -> 2.22.2 age adoption passing confidence
apollo-server-fastify 2.21.2 -> 2.22.2 age adoption passing confidence

Release Notes

apollographql/federation

v0.23.0

Compare Source

apollographql/apollo-server

v2.22.2

Compare Source

  • apollo-server-core: Fix a regression in v2.22.0 where combining apollo-server-core v2.22 with an older version of an integration package could lead to startup errors like called start() with surprising state invoking serverWillStart. The fix involves changing the semantics of the protected willStart method (which is left in only for backwards compatibility). Issue #​5065 Issue #​5066 PR #​5073

v2.22.1

Compare Source

  • apollo-server-core: Fix a regression in v2.22.0 where startup errors could be thrown as part of the GraphQL response instead of redacted in one edge case. PR #​5064

v2.22.0

Compare Source

  • Improve startup error handling by ensuring that your server has loaded its schema and executed its serverWillStart handlers successfully before starting an HTTP server. If you're using the apollo-server package, no code changes are necessary. If you're using an integration such as apollo-server-express that is not a "serverless framework", you can insert await server.start() between server = new ApolloServer() and server.applyMiddleware. (If you don't call server.start() yourself, your server will still work, but the previous behavior of starting a web server that may fail to load its schema still applies.) The serverless framework integrations (Lambda, Azure Functions, and Cloud Functions) do not support this functionality. While the protected method willStart still exists for backwards compatibility, you should replace calls to it with start or the new protected method ensureStarting. PR #​4981

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from da158f6 to d16df36 Compare March 26, 2021 03:06
@renovate renovate bot changed the title chore(deps): update dependency @apollo/gateway to ^0.25.0 chore(deps): update apollo graphql packages Mar 26, 2021
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 5 times, most recently from 4f71ee0 to a55ba5a Compare April 1, 2021 20:45
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from c4f139c to 1baa47e Compare April 2, 2021 22:27
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 1baa47e to 83e6b3d Compare April 5, 2021 20:01
@kamilmysliwiec kamilmysliwiec merged commit fa18db8 into master Apr 12, 2021
@delete-merged-branch delete-merged-branch bot deleted the renovate/apollo-graphql-packages branch April 12, 2021 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants