Packages

@appsignal/nodejs

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

Upgrading @appsignal/nodejs From 3.8.1 to 3.9.0

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.8.1Newest 3.x, Latest3.9.5
  1. 3.8.1yours
  2. 3.9.0target
1
change to make
0
advisories fixed
3
new
3
fixes

Before you upgrade

Tick each one off as you go
  • Breaking3.9.0

Security

Release by release

  1. 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.

1 other line 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

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.