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