@@ -92,21 +92,21 @@ also contains samples.
9292Our client libraries follow the [ Node.js release schedule] ( https://nodejs.org/en/about/releases/ ) .
9393Libraries are compatible with all current _ active_ and _ maintenance_ versions of
9494Node.js.
95+ If you are using an end-of-life version of Node.js, we recommend that you update
96+ as soon as possible to an actively supported LTS version.
9597
96- Client libraries targeting some end-of-life versions of Node.js are available, and
97- can be installed via npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
98- The dist-tags follow the naming convention ` legacy-(version) ` .
99-
100- _ Legacy Node.js versions are supported as a best effort:_
98+ Google's client libraries support legacy versions of Node.js runtimes on a
99+ best-efforts basis with the following warnings:
101100
102- * Legacy versions will not be tested in continuous integration.
103- * Some security patches may not be able to be backported.
104- * Dependencies will not be kept up-to-date, and features will not be backported .
101+ * Legacy versions are not tested in continuous integration.
102+ * Some security patches and features cannot be backported.
103+ * Dependencies cannot be kept up-to-date.
105104
106- #### Legacy tags available
107-
108- * ` legacy-8 ` : install client libraries from this dist-tag for versions
109- compatible with Node.js 8.
105+ Client libraries targeting some end-of-life versions of Node.js are available, and
106+ can be installed through npm [ dist-tags] ( https://docs.npmjs.com/cli/dist-tag ) .
107+ The dist-tags follow the naming convention ` legacy-(version) ` .
108+ For example, ` npm install @google-cloud/os-login@legacy-8 ` installs client libraries
109+ for versions compatible with Node.js 8.
110110
111111## Versioning
112112
0 commit comments