NPM LIBRARY
@risingstack/trace
Official package-registry history. This page does not infer support or EOL from release activity.
- Versions indexed
- 192
- Latest version activity
- 3.18.0
- Latest registry signal
- Published
- Last synchronized
- 25 Sep 2026
Authoritative registry
Version entries link to the official registry catalogue event that supplied the record.
Open package on npm ↗Lifecycle interpretation
Publication or deletion in a package registry is a distribution signal, not a promise of maintenance or security support. Any verified publisher EOL boundary remains in the main lifecycle catalogue.
Package-version activity
Newest official registry events first.
| Version | Registry event | Signal | Release notes | Evidence |
|---|---|---|---|---|
| 3.18.0 | 11 Sep 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.17.0 | 11 Sep 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.16.0 | 4 Aug 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.15.0 | 31 Jul 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.14.1-beta | 30 Jun 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.14.0 | 19 Jun 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.13.0 | 19 Jun 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.12.2 | 2 Jun 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.12.1 | 29 May 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.12.0-exponential-backoff.1 | 22 May 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.12.0-exponential-backoff.0 | 22 May 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.11.0 | 17 May 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.10.0 | 12 May 2017 | DEPRECATEDIncorrect status code reported in http instrumentation under circumstances. Please update | Not checked yet | Official event ↗ |
| 3.9.0 | 9 May 2017 | DEPRECATEDIncorrect status code reported in http instrumentation under circumstances. Please update | Not checked yet | Official event ↗ |
| 3.8.0 | 5 May 2017 | DEPRECATEDIncorrect status code reported in http instrumentation under circumstances. Please update | Not checked yet | Official event ↗ |
| 3.7.0 | 4 May 2017 | DEPRECATEDThis version has issues reporting topology edges. Please upgrade to >=3.10.0 | Not checked yet | Official event ↗ |
| 3.6.2 | 6 Apr 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.6.1 | 5 Apr 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.6.0 | 3 Apr 2017 | DEPRECATEDA bug in node-pre-gyp results in binaries not tested after download: https://github.com/RisingStack/trace-nodejs/issues/133 | Not checked yet | Official event ↗ |
| 3.5.3 | 23 Mar 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.5.2 | 21 Mar 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.5.1 | 2 Mar 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.5.1-beta.1 | 2 Mar 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.5.1-beta.0 | 2 Mar 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.5.0 | 22 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.5.0-beta.0 | 20 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.4.0 | 15 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.3.0 | 13 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.2.2 | 11 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.2.1 | 9 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.2.0 | 6 Feb 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.1.0 | 26 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.1.0-beta.5 | 24 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.1.0-beta.4 | 23 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.1.0-beta.3 | 23 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.0.5 | 18 Jan 2017 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 3.1.0-beta.2 | 16 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.1.0-beta.1 | 13 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.1.0-beta.0 | 13 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.0.5-beta.0 | 12 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.0.4 | 12 Jan 2017 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 3.0.4-beta.0 | 12 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.0.3-beta.0 | 12 Jan 2017 | PUBLISHED | Not checked yet | Official event ↗ |
| 3.0.3 | 9 Jan 2017 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 3.0.2 | 22 Dec 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 3.0.1 | 20 Dec 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 3.0.0 | 13 Dec 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.37.0-beta.2 | 12 Dec 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.36.0 | 25 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.35.0 | 25 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.34.0 | 22 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.33.1 | 22 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.33.0 | 16 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.32.0 | 16 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.31.0 | 11 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.30.0 | 11 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.29.0 | 11 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.28.0 | 7 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.6 | 7 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.5 | 3 Nov 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.4 | 24 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.3 | 20 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.2 | 18 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.1 | 18 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.27.0 | 18 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.26.0 | 18 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.25.0 | 17 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.24.0 | 13 Oct 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.23.4 | 19 Sep 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.23.3 | 1 Sep 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.23.2 | 30 Aug 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.23.1 | 29 Aug 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.23.0 | 25 Aug 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.22.0 | 16 Aug 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.21.0 | 12 Aug 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.20.0 | 10 Aug 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.19.1 | 28 Jul 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.19.0 | 27 Jul 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.18.4 | 4 Jul 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.18.3 | 30 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.18.2 | 29 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.18.1 | 29 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.18.0 | 29 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.17.0 | 28 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.16.2 | 22 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.16.1 | 21 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.16.0 | 20 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.15.3 | 15 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.15.2 | 13 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.15.1 | 8 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.15.0 | 1 Jun 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.14.2 | 30 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.14.1 | 30 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.14.0 | 27 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.13.3 | 22 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.13.2 | 22 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.13.1 | 22 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.13.0 | 20 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.12.1 | 17 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.12.0 | 10 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |