Update apollo package dependencies #2602
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the current versions of these dependencies rather than the alphas (from an alpha branch of the server repo) is causing multiple versions of some of these dependencies to appear in our platform repo's
release-federation
branch. I'm not certain this is the actual problem, but I do feel it brings us one step closer to resolving it.The error we're seeing in CI looks something like this, which leads me to suspect
apollo-env
(and other non-alpha apollo- packages):npm ls apollo-env
shows multiple versions in use (and possibly some bad de-duping?) I'm not sure why the deps aren't being met in some places.TODO: