This section provides an overview of how to keep your version of the Cloud Client Libraries for Node.js up-to-date with ongoing releases of Node.js. The Cloud Client Libraries for Node.js release schedule trails the Node.js release schedule.
For new development
New feature development uses the Active LTS described in the Node.js release schedule. Node.js Client libraries are also tested against all Maintenance LTS versions.
When starting a new project, choose the current Active LTS. If this version is not yet available on your chosen runtime, a Maintenance LTS version should be your second choice.
Keeping production systems current
Keeping your production systems on supported Node.js runtimes is the best way to ensure that you receive critical security and bug fixes. After a Node version goes end-of-life, the runtime will no longer receive critical updates.
Client libraries increment a major version when ending support for a Node.js runtime. An attempt is made to keep other breaking changes minimal. When a new major version of a library becomes available and ends support for your Node.js runtime, be sure to upgrade your runtime to a supported LTS version of Node.js, and upgrade your dependency. For more information, see Semantic Versioning.
Legacy support
Google's client libraries support legacy versions of Node.js runtimes on a best effort basis because it may not be possible to backport all patches. When possible, critical patches and bug fixes are released to prior major Node.js library versions.
Where to find version information
The latest versions and supported Node.js versions for Google Cloud libraries appear in the individual GitHub repositories for client libraries. You can also find a table of libraries that interact with individual Google Cloud services on the GitHub Google Cloud Client Library for Node.js page.