@@ -135,21 +135,21 @@ also contains samples.
135
135
Our client libraries follow the [ Node.js release schedule] ( https://nodejs.org/en/about/releases/ ) .
136
136
Libraries are compatible with all current _ active_ and _ maintenance_ versions of
137
137
Node.js.
138
+ If you are using an end-of-life version of Node.js, we recommend that you update
139
+ as soon as possible to an actively supported LTS version.
138
140
139
- Client libraries targeting some end-of-life versions of Node.js are available, and
140
- can be installed via npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
141
- The dist-tags follow the naming convention ` legacy-(version) ` .
142
-
143
- _ Legacy Node.js versions are supported as a best effort:_
141
+ Google's client libraries support legacy versions of Node.js runtimes on a
142
+ best-efforts basis with the following warnings:
144
143
145
- * Legacy versions will not be tested in continuous integration.
146
- * Some security patches may not be able to be backported.
147
- * Dependencies will not be kept up-to-date, and features will not be backported .
144
+ * Legacy versions are not tested in continuous integration.
145
+ * Some security patches and features cannot be backported.
146
+ * Dependencies cannot be kept up-to-date.
148
147
149
- #### Legacy tags available
150
-
151
- * ` legacy-8 ` : install client libraries from this dist-tag for versions
152
- compatible with Node.js 8.
148
+ Client libraries targeting some end-of-life versions of Node.js are available, and
149
+ can be installed through npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
150
+ The dist-tags follow the naming convention ` legacy-(version) ` .
151
+ For example, ` npm install @google-cloud/containeranalysis@legacy-8 ` installs client libraries
152
+ for versions compatible with Node.js 8.
153
153
154
154
## Versioning
155
155
0 commit comments