Heya folks!
We have a large federated micro-service setup using apollo-server v3, and we’re aware the v3 EoL is occurring in two weeks. We’re aware of course of the importance of staying up to date, but we’re resource constrained. Will us missing the deadline and continuing to run pods on v3 cause issues anywhere with Apollo’s services?
We use the Apollo Studio hosted schema registry, and publish to this when microservices change as well as pull from it in the startup of api-federation. This feels like the most likely cause of issue if there were to be any.
Thanks for all your help,
Theo
This is explained at https://www.apollographql.com/docs/apollo-server/previous-versions:
End-of-life versions will remain available in the npm registry and can still be installed and used in your projects. However, Apollo doesn’t guarantee any further support for them, nor does Apollo recommend their use. Additionally, Apollo doesn’t guarantee that GraphOS features will continue to work for packages beyond their end-of-life date.
No active efforts to break the use of Apollo Server v3 are planned at this time, but there are no guarantees going forward. Apollo Server v4 was released two years ago (today!) and there’s no better time than right now to upgrade.
1 Like
Amazing thank you - I’d not found that snippet 
Do you know if the team would typically make announcements ahead of breaking support for features such as this?
While we certainly do our best to ease impact and communicate well, the entire purpose of the deprecation/end-of-life cycle is that you should not depend on such communications if you do not choose to upgrade during the 2-year-long deprecation period.
1 Like