@@ -158,21 +158,21 @@ also contains samples.
158158Our client libraries follow the [ Node.js release schedule] ( https://nodejs.org/en/about/releases/ ) .
159159Libraries are compatible with all current _ active_ and _ maintenance_ versions of
160160Node.js.
161+ If you are using an end-of-life version of Node.js, we recommend that you update
162+ as soon as possible to an actively supported LTS version.
161163
162- Client libraries targeting some end-of-life versions of Node.js are available, and
163- can be installed via npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
164- The dist-tags follow the naming convention ` legacy-(version) ` .
165-
166- _ Legacy Node.js versions are supported as a best effort:_
164+ Google's client libraries support legacy versions of Node.js runtimes on a
165+ best-efforts basis with the following warnings:
167166
168- * Legacy versions will not be tested in continuous integration.
169- * Some security patches may not be able to be backported.
170- * Dependencies will not be kept up-to-date, and features will not be backported .
167+ * Legacy versions are not tested in continuous integration.
168+ * Some security patches and features cannot be backported.
169+ * Dependencies cannot be kept up-to-date.
171170
172- #### Legacy tags available
173-
174- * ` legacy-8 ` : install client libraries from this dist-tag for versions
175- compatible with Node.js 8.
171+ Client libraries targeting some end-of-life versions of Node.js are available, and
172+ can be installed through npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
173+ The dist-tags follow the naming convention ` legacy-(version) ` .
174+ For example, ` npm install @google-cloud/automl@legacy-8 ` installs client libraries
175+ for versions compatible with Node.js 8.
176176
177177## Versioning
178178
0 commit comments