@@ -103,21 +103,21 @@ also contains samples.
103
103
Our client libraries follow the [ Node.js release schedule] ( https://nodejs.org/en/about/releases/ ) .
104
104
Libraries are compatible with all current _ active_ and _ maintenance_ versions of
105
105
Node.js.
106
+ If you are using an end-of-life version of Node.js, we recommend that you update
107
+ as soon as possible to an actively supported LTS version.
106
108
107
- Client libraries targeting some end-of-life versions of Node.js are available, and
108
- can be installed via npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
109
- The dist-tags follow the naming convention ` legacy-(version) ` .
110
-
111
- _ Legacy Node.js versions are supported as a best effort:_
109
+ Google's client libraries support legacy versions of Node.js runtimes on a
110
+ best-efforts basis with the following warnings:
112
111
113
- * Legacy versions will not be tested in continuous integration.
114
- * Some security patches may not be able to be backported.
115
- * Dependencies will not be kept up-to-date, and features will not be backported .
112
+ * Legacy versions are not tested in continuous integration.
113
+ * Some security patches and features cannot be backported.
114
+ * Dependencies cannot be kept up-to-date.
116
115
117
- #### Legacy tags available
118
-
119
- * ` legacy-8 ` : install client libraries from this dist-tag for versions
120
- compatible with Node.js 8.
116
+ Client libraries targeting some end-of-life versions of Node.js are available, and
117
+ can be installed through npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
118
+ The dist-tags follow the naming convention ` legacy-(version) ` .
119
+ For example, ` npm install @google-cloud/managed-identities@legacy-8 ` installs client libraries
120
+ for versions compatible with Node.js 8.
121
121
122
122
## Versioning
123
123
0 commit comments