Stay organized with collections
Save and categorize content based on your preferences.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Supported Node.js versions\n\nThis section provides an overview of how to keep your version of the\nCloud Client Libraries for Node.js up-to-date with ongoing releases of Node.js.\nThe Cloud Client Libraries for Node.js release schedule trails the Node.js\nrelease schedule.\n\nFor new development\n-------------------\n\nNew feature development uses the Active LTS described in the Node.js\nrelease schedule. Node.js Client libraries are also tested against all\nMaintenance LTS versions.\n\nWhen starting a new project, choose the current Active LTS. If\nthis version is not yet available on your chosen runtime, a\nMaintenance LTS version should be your second choice.\n| **Note:** Be sure to use even-numbered Node.js releases. Avoid Node.js odd-numbered releases because they do not represent LTS candidates and become end-of-life after 6 months.\n\nKeeping production systems current\n----------------------------------\n\nKeeping your production systems on supported Node.js runtimes is the best way to\nensure that you receive critical security and bug fixes. After a Node version\ngoes end-of-life, the runtime will no longer receive critical updates.\n\nClient libraries increment a major version when ending support for a Node.js runtime.\nAn attempt is made to keep other breaking changes minimal. When a new major\nversion of a library becomes available and ends support for your Node.js\nruntime, be sure to upgrade your runtime to a supported LTS version of Node.js,\nand upgrade your dependency. For more information, see\n[Semantic Versioning](https://semver.org/).\n\n### Legacy support\n\nGoogle's client libraries support legacy versions of Node.js runtimes on a best\neffort basis because it may not be possible to backport all patches.\nWhen possible, critical patches and bug fixes are released to prior major\nNode.js library versions.\n\n### Where to find version information\n\nThe latest versions and supported Node.js versions for Google Cloud\nlibraries appear in the individual GitHub repositories for client libraries.\nYou can also find a table of libraries that interact with individual\nGoogle Cloud services on the\n[GitHub Google Cloud Client Library for Node.js](https://github.com/googleapis/google-cloud-node) page."]]
