Packages

@appsignal/opentelemetry-instrumentation-bullmq

0.9.0 · 24 Aug 2026Apache-2.0125.3k / weekRepositoryHomepagenpmAtom feed

Upgrading @appsignal/opentelemetry-instrumentation-bullmq From 0.7.0 to 0.9.0

5 releases in betweenevery note read

0
changes to make
0
advisories fixed
1
new
3
fixes

Release by release

  1. 0.8.0 – 0.9.02 releases, nothing new or fixed in the notes

  2. 0.7.3

    8 Oct 20241 new
    • New

      Add a useProducerSpanAsConsumerParent configuration option that defaults to false. When set to true, instead of establishing a span link from the consumer span to the producer span, the consumer span will be in the same trace, as a child span of the producer span. (patch 5d7ee27)

  3. 0.7.2

    1 Oct 20241 fix
    • Fixed

      Fix importing the package as an ESM module. (patch 814d93a)

  4. 0.7.1

    13 Jun 20242 fixes
    • Fixed

      Mark BullMQ peer dependency as optional.

    • Fixed

      Do not reexport bullmq types.

5 other lines we could not sort, mostly version bumps
  • Declare @opentelemetry/api as a peer dependency instead of a regular dependency, so that npm installs one copy of it, shared with your application.

    0.9.0
  • Update the bundled @opentelemetry/instrumentation and @opentelemetry/semantic-conventions packages to their current versions. The span attributes this instrumentation emits are unchanged.

    0.9.0
  • Update OpenTelemetry dependencies to v2. (minor b85d788)

    0.8.0
  • Replace the messaging.bullmq.job.parentOpts.waitChildrenKey span attribute with messaging.bullmq.job.parentOpts.addToWaitingChildren. The old attribute reported an internal Redis key string (bull:<queue>:waiting-children) that bullmq exposed up to version 5.61.2. From 5.62.0, bullmq replaced it with an addToWaitingChildren boolean flag. The new attribute normalises both representations into a single boolean: true when a flow parent job is waiting for its children to complete. (minor af9eadb)

    0.8.0
  • Update messaging semantic convention attributes to latest OpenTelemetry Semantic Conventions for Messaging Spans spec.

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