|
1 | 1 | # `dd-trace`: Node.js APM Tracer Library |
2 | 2 |
|
3 | | -[](https://www.npmjs.com/package/dd-trace) |
| 3 | +[](https://www.npmjs.com/package/dd-trace) |
| 4 | +[](https://www.npmjs.com/package/dd-trace/v/latest-node12) |
4 | 5 | [](https://www.npmjs.com/package/dd-trace/v/latest-node12) |
5 | 6 | [](https://www.npmjs.com/package/dd-trace/v/dev) |
6 | 7 | [](https://codecov.io/gh/DataDog/dd-trace-js) |
@@ -28,27 +29,28 @@ Most of the documentation for `dd-trace` is available on these webpages: |
28 | 29 | | :---: | :---: | :---: | :---: | :---: | :---: | |
29 | 30 | | [`v1`](https://github.com/DataDog/dd-trace-js/tree/v1.x) |  | `>= v12` | **End of Life** | 2021-07-13 | 2022-02-25 | |
30 | 31 | | [`v2`](https://github.com/DataDog/dd-trace-js/tree/v2.x) |  | `>= v12` | **Maintenance** | 2022-01-28 | 2023-08-15 | |
31 | | -| [`v3`](https://github.com/DataDog/dd-trace-js/tree/v3.x) |  | `>= v14` | **Current** | 2022-08-15 | Unknown | |
| 32 | +| [`v3`](https://github.com/DataDog/dd-trace-js/tree/v3.x) |  | `>= v14` | **Maintenance** | 2022-08-15 | 2024-05-15 | |
| 33 | +| [`v4`](https://github.com/DataDog/dd-trace-js/tree/v4.x) |  | `>= v16` | **Current** | 2023-05-12 | Unknown | |
32 | 34 |
|
33 | | -We currently maintain two release lines, namely `v2` and `v3`. |
34 | | -Features and bug fixes that are merged are released to the `v3` line and, if appropriate, also the `v2` line. |
| 35 | +We currently maintain three release lines, namely `v2`, `v3` and `v4`. |
| 36 | +Features and bug fixes that are merged are released to the `v4` line and, if appropriate, also the `v2` and `v3` line. |
35 | 37 |
|
36 | | -For any new projects it is recommended to use the `v3` release line: |
| 38 | +For any new projects it is recommended to use the `v4` release line: |
37 | 39 |
|
38 | 40 | ```sh |
39 | 41 | $ npm install dd-trace |
40 | 42 | $ yarn add dd-trace |
41 | 43 | ``` |
42 | 44 |
|
43 | | -However, existing projects that already use the `v2` release line, or projects that need to support Node.js v12, may use the `v2` release line. |
| 45 | +However, existing projects that already use the `v2` or `v3` release lines, or projects that need to support EOL versions of Node.js, may continue to use these release lines. |
44 | 46 | This is done by specifying the version when installing the package. |
45 | | -Note that we also publish to npm using a `latest-node12` tag that can also be used for install: |
| 47 | +Note that we also publish to npm using a `latest-node12` and `latest-node14` tag that can also be used for install: |
46 | 48 |
|
47 | 49 | ```sh |
48 | | -$ npm install dd-trace@2 |
49 | | -$ yarn add dd-trace@2 |
50 | | -$ npm install dd-trace@latest-node12 |
51 | | -$ yarn add dd-trace@latest-node12 |
| 50 | +$ npm install dd-trace@3 |
| 51 | +$ yarn add dd-trace@3 |
| 52 | +$ npm install dd-trace@latest-node14 |
| 53 | +$ yarn add dd-trace@latest-node14 |
52 | 54 | ``` |
53 | 55 |
|
54 | 56 | Any backwards-breaking functionality that is introduced into the library will result in an increase of the major version of the library and therefore a new release line. |
|
0 commit comments