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