Packages

@appsignal/nodejs

3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed

Upgrading @appsignal/nodejs From 1.3.1 to 3.9.5

100 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 1.3.1Newest 1.x1.3.2
  1. 1.3.1yours
  2. 1 release
  3. 2.0.0major
  4. 23 releases
  5. 3.0.0major
  6. 68 releases
  7. 3.9.0security
  8. 2 releases
  9. 3.9.3security
  10. 3.9.4security
  11. 3.9.5target

Start here

Before you upgrade

Tick each one off as you go
  • Breaking3.9.0
  • Breaking3.6.4
  • Breaking3.6.0
  • Breaking3.2.0
  • Breaking3.0.30
  • Breaking3.0.26
  • Breaking3.0.7
  • Breaking2.3.2
  • Breaking2.3.2
  • Breaking2.3.2

Security

Release by release

  1. 3.9.5

    11 Nov 20261 fix
    • Fixed

      Fix a crash when setCustomData, setParams or setSessionData is called with a value that contains a BigInt. BigInt values are now stored as "bigint:<n>", the same format used for metric tags and log attributes.

  2. 3.9.4

    Security fix23 Oct 2026
    • Security

      Bump the bundled certificates that the agent uses when it can't open the configured CA file. They no longer include the emSign ECC Root CA - G3 and AAA Certificate Services root certificates, which compromised eMudhra intermediate certificates chain to.

  3. 3.9.3

    Security fix22 Oct 2026
    • Security

      Stop trusting certificates issued under the eMudhra intermediate certificate authorities whose private keys were compromised in October 2026. The bundled CA certificates no longer include the emSign ECC Root CA - G3 root certificate, which those intermediates chain to. (patch 498c087, 0178413, b9cbfeb)

  4. 3.9.2

    14 Oct 20261 new · 3 fixes
    • New

      Automatically detect the application's revision from the HEROKU_BUILD_COMMIT environment variable, which is set by Heroku at build time when the runtime-dyno-build-metadata Heroku Labs feature is enabled.

    • Fixed

      Improve handling of the extension internal queue when full. (patch 30f9e93)

    • Fixed

      Fix issues in the extension that lead to gaps in data reporting. (patch 3a91e18)

    • Fixed

      Fix an extension crash when the same span is used from multiple threads at the same time. (patch 582483d)

  5. 3.9.1

    10 Sep 20261 fix
    • Fixed

      Fix the sanitization of function arguments in SQL statements.

  6. 3.9.0

    Security fix8 Sep 20263 new · 3 fixes
    • Security

      CVE-2026-59892 in @opentelemetry/propagator-jaeger, which this integration does not use but did bundle through @opentelemetry/sdk-node.

    • Security

      CVE-2026-54285 in @opentelemetry/core, which applies to the W3C baggage propagation that this integration does use.

    • Breaking

      Drop support for Node.js 18. The minimum supported version is now Node.js 20.6.0, which is what the bundled OpenTelemetry packages require.

    • New

      Report queue events from applications that use BullMQ's own telemetry, which is what BullMQ version 6 and newer offer through the bullmq-otel package. These were previously reported as uncategorised events named after the raw span, because BullMQ describes its spans with its own attributes rather than the OpenTelemetry messaging conventions. They are now named and categorised the same way as events from the @appsignal/opentelemetry-instrumentation-bullmq package.

  7. 3.8.1

    10 Jun 20263 fixes
    • Fixed

      Continue reporting non-disk host metrics when a mount is frozen. (patch a4a652d)

    • Fixed

      Fix host-metrics leaking zombie [timeout] processes in Alpine linux containers.

    • Fixed

      Ensure sendError ends its span even when the callback throws. (patch e9c0209)

  8. 3.8.0nothing new or fixed in the note

119 other lines we could not sort, mostly version bumps
  • Update the agent to handle high traffic apps. On high-traffic apps that would exceed the maximum accepted internal payload size, send data to the Push API more frequently. (patch 96d9030)

    3.9.0
  • Update OpenTelemetry dependencies to v2. All bundled OpenTelemetry packages have been updated to their OpenTelemetry v2-compatible versions. This resolves compatibility issues when third-party span processors or instrumentations are used alongside AppSignal, which could cause spans to silently drop due to v1/v2 incompatibilities. The @opentelemetry/instrumentation-redis-4 package has been removed. Redis v4 instrumentation is now handled by @opentelemetry/instrumentation-redis, which supports both Redis v3 and v4. (minor efbcc4a)

    3.8.0
  • Bundled certificates have been updated. (patch 498c087)

    3.8.0
  • Update BullMQ OpenTelemetry extractor to support new messaging semantic conventions. (patch 3702e4d)

    3.8.0
  • Use system-specific operation name in messaging span names.

    3.8.0
  • Require parent spans on database and outgoing HTTP instrumentations that support it. When a database query is performed using the ioredis, pg, redis or mongoose libraries, or when an outgoing HTTP request is performed using the http module, a span will only be created if a trace has already been started in the current active context, that is, if the span to be created would have a parent.

    3.7.4
  • Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt, or plaintext format. No further config needed when calling our logger, like so:

    3.7.2
  • Update the OpenTelemetry dependency to version 1.9 of the OpenTelemetry API. This improves compatibility with instrumentation libraries that depend on this version of the API. (patch 4cc4257)

    3.7.1
  • Disable the OpenTelemetry trace context propagation across applications. If multiple applications are instrumented with AppSignal for Node.js using OpenTelemetry, the propagation across applications could lead to application data being reported the wrong application in AppSignal. (minor 7fc85b8, 7ddcbec)

    3.7.0
  • Remove redundant cron check-in pairs. When more than one pair of start and finish cron check-in events is reported for the same identifier in the same period, only one of them will be reported to AppSignal. (patch 1cfcc0a)

    3.6.5

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.