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