Skip to content

chore(deps)(deps): bump the production-deps group across 1 directory with 16 updates - #1103

Open
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/production-deps-65ee967581
Open

dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/production-deps-65ee967581

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026 •

Copy link
Copy Markdown

Bumps the production-deps group with 16 updates in the / directory:

Package From To
@nestjs/throttler 6.5.0 6.7.1
@opentelemetry/api 1.9.1 1.10.0
@opentelemetry/auto-instrumentations-node 0.77.0 0.82.0
@opentelemetry/core 2.10.0 2.12.0
@opentelemetry/exporter-trace-otlp-http 0.219.0 0.300.0
@opentelemetry/resources 2.10.0 2.12.0
@opentelemetry/sdk-node 0.219.0 0.300.0
@opentelemetry/semantic-conventions 1.43.0 1.44.0
@prisma/adapter-pg 7.9.1 7.10.1
@prisma/client 7.9.0 7.10.1
@stellar/stellar-sdk 17.1.0 17.4.0
axios 1.18.1 1.21.0
compression 1.8.1 1.8.2
express 5.2.1 5.3.0
pg 8.22.0 8.23.1
zod 4.4.3 4.6.7

Updates @nestjs/throttler from 6.5.0 to 6.7.1

Release notes

Sourced from @​nestjs/throttler's releases.

v6.7.1

Patch Changes

  • e8368b3: Set rate limit headers through res.setHeader() when the response has no res.header() method, so the guard no longer throws res.header is not a function on custom HTTP adapters. The logic lives in a new protected setResponseHeader() method that subclasses can override.
  • a482ef9: Coerce numeric strings for limit, ttl and blockDuration to numbers, as returned for example by ConfigService.get<number>() for environment variables. Previously Date.now() + '60000' concatenated instead of adding, which silently corrupted every expiry and X-RateLimit-Reset. A value that is not numeric now fails with an error naming the option and the throttler.
  • a9a28b9: Respect an explicit 0 for limit, ttl and blockDuration in @Throttle() and the module options instead of falling back to the default. blockDuration: 0 now means "no extra block": the in-memory storage rejects requests while the window is full and lets them through again as soon as the oldest hit expires, without recording the rejected ones.
  • bf81677: Import shared interfaces from the public Nest package entry point for Nest 12 compatibility.
  • caaabc9: Stop the in-memory storage from retaining request contexts. It used to schedule one setTimeout per counted hit, and each timer kept the request's AsyncLocalStorage stores (for example an ORM's per-request entity manager) in memory until the TTL expired. It now records when each hit expires and prunes expired hits on access. The idle-record sweep is also no longer tied to the context of the first request. With blockDuration: 0, Retry-After now reports when the oldest hit expires rather than when the window ends.
  • 7703c10: Log a warning when no throttler is configured. The guard limits nothing in that case and previously said nothing at boot, so ThrottlerModule.forRoot() and ThrottlerModule.forRoot([]) looked like a working setup.

v6.7.0

Minor Changes

  • 7004a97: Normalize IPv6 source addresses in the default tracker, and evict expired records from the in-memory storage.

    The built-in getTracker returned req.ip verbatim, so a client holding an IPv6 allocation could send every request from a different address within its own subnet and never share a counter, defeating the rate limit. Addresses are now masked to a /64 before being used as the tracker; the prefix length is configurable via the new ipv6SubnetPrefix module option. IPv4 addresses, IPv4-mapped addresses, the loopback, and custom getTracker implementations are unaffected.

    ThrottlerStorageService also never removed records, so a stream of requests from distinct trackers grew the internal map for the lifetime of the process. Idle records are now swept out once their window has fully elapsed. Limiting behaviour is unchanged: a record is only dropped after every pending hit has expired and any block has lapsed.

    Note that the tracker string for IPv6 clients changes shape (2001:db8:0:1::/64), so storage keys rotate once on upgrade.

v6.6.0

Minor Changes

  • c342bad: Declare the supported Node versions in engines, matching the range the CI matrix tests
  • c625e98: Update to allow for support for Nest version 12
Changelog

Sourced from @​nestjs/throttler's changelog.

6.7.1

Patch Changes

  • e8368b3: Set rate limit headers through res.setHeader() when the response has no res.header() method, so the guard no longer throws res.header is not a function on custom HTTP adapters. The logic lives in a new protected setResponseHeader() method that subclasses can override.
  • a482ef9: Coerce numeric strings for limit, ttl and blockDuration to numbers, as returned for example by ConfigService.get<number>() for environment variables. Previously Date.now() + '60000' concatenated instead of adding, which silently corrupted every expiry and X-RateLimit-Reset. A value that is not numeric now fails with an error naming the option and the throttler.
  • a9a28b9: Respect an explicit 0 for limit, ttl and blockDuration in @Throttle() and the module options instead of falling back to the default. blockDuration: 0 now means "no extra block": the in-memory storage rejects requests while the window is full and lets them through again as soon as the oldest hit expires, without recording the rejected ones.
  • bf81677: Import shared interfaces from the public Nest package entry point for Nest 12 compatibility.
  • caaabc9: Stop the in-memory storage from retaining request contexts. It used to schedule one setTimeout per counted hit, and each timer kept the request's AsyncLocalStorage stores (for example an ORM's per-request entity manager) in memory until the TTL expired. It now records when each hit expires and prunes expired hits on access. The idle-record sweep is also no longer tied to the context of the first request. With blockDuration: 0, Retry-After now reports when the oldest hit expires rather than when the window ends.
  • 7703c10: Log a warning when no throttler is configured. The guard limits nothing in that case and previously said nothing at boot, so ThrottlerModule.forRoot() and ThrottlerModule.forRoot([]) looked like a working setup.

6.7.0

Minor Changes

  • 7004a97: Normalize IPv6 source addresses in the default tracker, and evict expired records from the in-memory storage.

    The built-in getTracker returned req.ip verbatim, so a client holding an IPv6 allocation could send every request from a different address within its own subnet and never share a counter, defeating the rate limit. Addresses are now masked to a /64 before being used as the tracker; the prefix length is configurable via the new ipv6SubnetPrefix module option. IPv4 addresses, IPv4-mapped addresses, the loopback, and custom getTracker implementations are unaffected.

    ThrottlerStorageService also never removed records, so a stream of requests from distinct trackers grew the internal map for the lifetime of the process. Idle records are now swept out once their window has fully elapsed. Limiting behaviour is unchanged: a record is only dropped after every pending hit has expired and any block has lapsed.

    Note that the tracker string for IPv6 clients changes shape (2001:db8:0:1::/64), so storage keys rotate once on upgrade.

6.6.0

Minor Changes

  • c342bad: Declare the supported Node versions in engines, matching the range the CI matrix tests
  • c625e98: Update to allow for support for Nest version 12

6.4.0

6.5.1

Patch Changes

  • 603cb82: handles edge case where multiple clients making frequent requests interfere with each other
Commits
  • 91f4912 Merge pull request #2706 from nestjs/changeset-release/master
  • c5e8c90 chore: version packages
  • 9ec3aa3 Merge pull request #2668 from nestjs/renovate/major-nest-monorepo
  • 5d3b9ae Merge pull request #2712 from nestjs/fix/coerce-numeric-options
  • 4335230 Merge pull request #2711 from nestjs/fix/timer-free-storage
  • a482ef9 fix(guard): coerce numeric string options
  • e082222 chore(deps): update nest monorepo to v12
  • caaabc9 fix(storage): do not retain request contexts in timers
  • 4ab8c63 Merge pull request #2697 from nestjs/renovate/node-24.x
  • c36f011 Merge pull request #2703 from nestjs/renovate/nest-graphql-monorepo
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​nestjs/throttler since your current version.


Updates @opentelemetry/api from 1.9.1 to 1.10.0

Release notes

Sourced from @​opentelemetry/api's releases.

api/v1.10.0

1.10.0

🚀 Features

  • feat(api): integrate the Logs API into @opentelemetry/api #4862 @​hectorhdzg
  • feat(api): add imperative context.attach() for setting context across callback boundaries that with() cannot wrap. #6845 @​pichlermarc
    • attach() returns a Token whose dispose() method restores the previous context. Use token.dispose() to detach.
    • attach is an optional method on the ContextManager interface; when the active context manager does not implement it, context.attach() logs a warning and returns a no-op token.
  • feat(api): add AnyValue type (of type unknown) and extend Attributes type values to use AnyValue #6780 @​trentm
    • This is part of supporting OTEP 4485.
    • This is a breaking change for SDK implementations, in that they may need to support more attribute types for any APIs that accept Attributes or AnyValue. Implementors should refer to the OTEP 4485 link above for "MUST / SHOULD" requirements for complex attributes handling. See also the attributes-handling utilities provided by @opentelemetry/core to help. For example, cleanSimpleAttributes() can be used to limit user-provided attributes to the set of value types supported in earlier @opentelemetry/api versions.
    • This change is typically not a breaking change for users of @opentelemetry/api. There is one possible breaking case: If a TypeScript user was using the Attributes type in their own code and using TypeScript Narrowing to reduce an attribute value to an expected type (example here). It is expected that this usage should be rare and, likely, limited to SDK implementations, if at all. (If this impacted your code, please let us know.)
    • Note for users of attributes: Simple attributes SHOULD be used whenever possible. Instrumentations SHOULD assume that backends do not index individual properties of complex attributes, that querying or aggregating on such properties is inefficient and complicated, and that reporting complex attributes carries higher performance overhead.

🐛 Bug Fixes

  • fix(api): cap tracestate list-members and total length in the deprecated TraceState.set() so it stays in step with TraceState from @opentelemetry/core #6964 @​Zuhef
  • fix: resolve the ESM build through the default export condition instead of import, so a resolver that activates neither import nor require still finds an entry point #7132 @​overbalance

📚 Documentation

  • docs(api): complete @since annotations for the public API #7023 @​nabeelamjadsheikh
    • Adds the three missing exported-type annotations and the member-level annotations for methods and properties introduced after their enclosing type.
    • Corrects Attributes, AttributeValue and TracerOptions from 1.3.0 to 1.1.0; all three were already importable in 1.1.0 via wildcard re-export.

🏠 Internal

  • build: migrate the package build from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory #6293 @​overbalance
    • The public entry points are unchanged: @opentelemetry/api and @opentelemetry/api/experimental. This package already declared an exports map, so deep imports such as @opentelemetry/api/build/src/... were rejected before this change and continue to be.
    • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations. The non-standard esnext condition has been dropped in favour of the standard import/require conditions.
  • perf(api): add getGlobal fast-path #6956 @​legendecas
  • chore: remove the redundant module field from package.json; bundlers resolve the ESM build through the exports map #7130 @​overbalance
Changelog

Sourced from @​opentelemetry/api's changelog.

1.10.0

🚀 (Enhancement)

🐛 (Bug Fix)

  • fix(core): added falsy check to make otel core work with browser where webpack config had process as false or null #3613 @​ravindra-dyte
  • fix(instrumentation-http): include query params in http.target #3646 @​kobi-co

📚 (Refine Doc)

🏠 (Internal)

Commits
  • 56e6b1b chore: Release API 1.4.1, SDK 1.10.0, Experimental 0.36.0 (#3654)
  • ecb5ebe fix: Minor typing issues for web sandbox (#3660)
  • 48ecf22 feat(sdk-trace-base): add dropped attributes and events count on span (#3576)
  • 95bf6fc fix(build): add example/http to ignore list in update-ts-configs (#3657)
  • 3a2ca58 feat: add unit to view instrument selection criteria (#3647)
  • ebc8575 chore(jeager-exporter): deprecate jaeger exporter (#3585)
  • 2f715bd feat: allow to add attributes from grpc metadata in the patched server (#3589)
  • cbbdfd3 fix(sdk-node): update instrumentations once MeterProvider is initialized (#3624)
  • 4a4484a chore: update http example (#3651)
  • 494efff fix(otlp-exporter-base): fix changelog for merged retry pr (#3650)
  • Additional commits viewable in compare view

Updates @opentelemetry/auto-instrumentations-node from 0.77.0 to 0.82.0

Changelog

Sourced from @​opentelemetry/auto-instrumentations-node's changelog.

0.82.0 (2026-10-20)

⚠ BREAKING CHANGES

  • bump versions to SDK 3.0/API 1.10.0 (#3839)
  • raise minimum supported Node.js to 22.15.0, dropping 18 and 20 support (#3847)

Miscellaneous Chores

  • bump versions to SDK 3.0/API 1.10.0 (#3839) (cfdbfcc)
  • raise minimum supported Node.js to 22.15.0, dropping 18 and 20 support (#3847) (79dc211)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @​opentelemetry/instrumentation-amqplib bumped from ^0.70.0 to ^0.71.0
      • @​opentelemetry/instrumentation-aws-lambda bumped from ^0.75.0 to ^0.76.0
      • @​opentelemetry/instrumentation-aws-sdk bumped from ^0.78.0 to ^0.79.0
      • @​opentelemetry/instrumentation-bunyan bumped from ^0.68.0 to ^0.69.0
      • @​opentelemetry/instrumentation-cassandra-driver bumped from ^0.68.0 to ^0.69.0
      • @​opentelemetry/instrumentation-connect bumped from ^0.66.0 to ^0.67.0
      • @​opentelemetry/instrumentation-cucumber bumped from ^0.39.0 to ^0.40.0
      • @​opentelemetry/instrumentation-dataloader bumped from ^0.40.0 to ^0.41.0
      • @​opentelemetry/instrumentation-dns bumped from ^0.66.0 to ^0.67.0
      • @​opentelemetry/instrumentation-express bumped from ^0.71.1 to ^0.72.0
      • @​opentelemetry/instrumentation-fs bumped from ^0.42.0 to ^0.43.0
      • @​opentelemetry/instrumentation-generic-pool bumped from ^0.66.0 to ^0.67.0
      • @​opentelemetry/instrumentation-graphql bumped from ^0.71.0 to ^0.72.0
      • @​opentelemetry/instrumentation-hapi bumped from ^0.69.0 to ^0.70.0
      • @​opentelemetry/instrumentation-host-metrics bumped from ^0.6.0 to ^0.7.0
      • @​opentelemetry/instrumentation-ioredis bumped from ^0.71.0 to ^0.72.0
      • @​opentelemetry/instrumentation-kafkajs bumped from ^0.32.0 to ^0.33.0
      • @​opentelemetry/instrumentation-knex bumped from ^0.67.0 to ^0.68.0
      • @​opentelemetry/instrumentation-koa bumped from ^0.71.0 to ^0.72.0
      • @​opentelemetry/instrumentation-lru-memoizer bumped from ^0.67.0 to ^0.68.0
      • @​opentelemetry/instrumentation-memcached bumped from ^0.66.0 to ^0.67.0
      • @​opentelemetry/instrumentation-mongodb bumped from ^0.76.0 to ^0.77.0
      • @​opentelemetry/instrumentation-mongoose bumped from ^0.69.0 to ^0.70.0
      • @​opentelemetry/instrumentation-mysql bumped from ^0.69.1 to ^0.70.0
      • @​opentelemetry/instrumentation-mysql2 bumped from ^0.69.0 to ^0.70.0
      • @​opentelemetry/instrumentation-nestjs-core bumped from ^0.70.0 to ^0.71.0
      • @​opentelemetry/instrumentation-net bumped from ^0.67.0 to ^0.68.0
      • @​opentelemetry/instrumentation-openai bumped from ^0.21.0 to ^0.22.0
      • @​opentelemetry/instrumentation-oracledb bumped from ^0.48.0 to ^0.49.0
      • @​opentelemetry/instrumentation-pg bumped from ^0.76.0 to ^0.77.0
      • @​opentelemetry/instrumentation-pino bumped from ^0.69.0 to ^0.70.0
      • @​opentelemetry/instrumentation-redis bumped from ^0.71.0 to ^0.72.0

... (truncated)

Commits

Updates @opentelemetry/core from 2.10.0 to 2.12.0

Release notes

Sourced from @​opentelemetry/core's releases.

v2.12.0

2.12.0

🚀 Features

  • chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #7086

🏠 Internal

  • feat(ci): support releasing from maintenance branches #6767 @​pichlermarc
    • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.

v2.11.0

2.11.0

🚀 Features

  • feat(context-async-hooks): implement attach() on AsyncLocalStorageContextManager #6845 @​pichlermarc
    • On Node.js 25.9+, delegates to AsyncLocalStorage.withScope() returning a native RunScope. On older Node.js, falls back to enterWith() with a manual disposable wrapper.
  • feat(sdk-trace): allow configuring the force flush timeout per call #6929 @​LarryHu0217

🐛 Bug Fixes

  • fix(sdk-metrics): ignore Infinity in exponential histograms #7015 @​mwear

🏠 Internal

  • perf(sdk-metrics): reuse a single DataView for exponential histogram bit reads #6998 @​mwear
  • chore(ci): run documentation tests on a weekly schedule #6920 @​LarryHu0217
  • feat(ci): support pre-releases and major version bumps in the release workflow #6768 @​pichlermarc
  • chore(resources): Ensure that multiple uses of serviceInstanceIdDetector.detect() return the same value for service.instance.id
Changelog

Sourced from @​opentelemetry/core's changelog.

CHANGELOG

All notable changes to this project will be documented in this file.

For API changes, see the API CHANGELOG. For experimental package changes, see the experimental CHANGELOG. For semantic convention package changes, see the semconv CHANGELOG. For notes on migrating to 2.x / 0.200.x see the upgrade guide. For notes on migrating to 3.x see the 3.x migration guide.

Unreleased

💥 Breaking Changes

🚀 Features

  • feat(resources): Deprecate envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetector as stable (the service.instance.id semconv attribute is now stable). #6999 @​trentm

🐛 Bug Fixes

  • fix(core): accept attribute values with shared (non-circular) object references #7068 @​rajanpanth

📚 Documentation

🏠 Internal

3.0.0

💥 Breaking Changes

  • chore(sdk-trace-node)!: remove the @opentelemetry/sdk-trace-node package #7054
    • The sdk-trace-node package has been replaced by the @opentelemetry/sdk-trace package. See the 3.x migration guide for full migration instructions.
  • chore(shim-opentracing)!: remove the @opentelemetry/shim-opentracing package
  • chore(context-async-hooks)!: remove the unused class AsyncHooksContextManager #7078
  • feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
    • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
    • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
    • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
    • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
    • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
    • If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
  • feat(core)!: remove deprecated getTimeOrigin, otperformance, _globalThis, and unrefTimer from @opentelemetry/core #7053

... (truncated)

Commits
  • 92b844e chore: prepare next v2.x release (#7151)
  • a859aff fix(web-common): export getElementXPath utility (#7124)
  • 2bd5a73 chore(web-common)!: deprecate addSpanNetworkEvents() et al instrumentation-...
  • d60f05e doc(sdk-trace): add description for StackContextManager (#7089)
  • 5bd476e chore: move context manager to sdk-trace (#7086)
  • 554c0c6 chore: move sdk-trace-web utils to web-common (#7058)
  • 788922c ci: support maintenance branch releases (#7036)
  • 0b72a81 chore: prepare next release (#7044)
  • a9c5338 ci: roll prerelease changelog into one final release changelog (#7045)
  • f41805e chore: prepare next release (#7042)
  • Additional commits viewable in compare view

Updates @opentelemetry/exporter-trace-otlp-http from 0.219.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/exporter-trace-otlp-http's releases.

experimental/v0.300.0

0.300.0

Summary

  • The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
  • The public interface has changed
  • Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

  • chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
    • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
  • feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
    • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
    • NodeSDKConfiguration.metricReader — use metricReaders instead.
    • NodeSDKConfiguration.spanProcessor — use spanProcessors instead.
    • export * as node from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-node instead.
    • export * as tracing from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-base instead.
  • feat(sdk-logs)!: remove deprecated SdkLogRecord type alias and LoggerProviderConfig type alias #7062
    • SdkLogRecord — use ReadWriteLogRecord instead.
    • LoggerProviderConfig — use LoggerProviderOptions instead.
  • feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
    • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
    • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/sdk-logs/build/src/... or @opentelemetry/sdk-logs/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
    • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
    • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
    • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
    • Packages that ship separate Node.js and browser implementations export them under explicit subpaths, for example @opentelemetry/sdk-logs/platform. If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
  • feat(sdk-node)!: remove "jaeger" propagator from @opentelemetry/sdk-node #7077
    • OTEL_PROPAGATORS=jaeger and { jaeger: null } in the configuration object are no longer recognised. Replace with "tracecontext".
    • See the 3.x migration guide for full instructions.
  • fix(opentelemetry-exporter-prometheus)!: default exporter host to localhost #6599 @​cjihrig
  • chore!: bump minimum node.js version to >=22.15.0
  • feat(api-logs)!: move the Logs API to @opentelemetry/api and remove the standalone @opentelemetry/api-logs package #4862 @​hectorhdzg
  • fix(exporter-prometheus)!: stop reading Prometheus exporter host and port environment variables in the exporter constructor #6966 @​LarryHu0217
  • chore(web-common)!: clean up and deprecate network span utils #7114
    • These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
    • Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents().
  • feat(sdk-node)!: drop SDK package re-exports (api, contextBase, core, logs, metrics, resources) #7111 @​pichlermarc
    • api / contextBase → import from @opentelemetry/api
    • core → import from @opentelemetry/core
    • logs → import from @opentelemetry/sdk-logs
    • metrics → import from @opentelemetry/sdk-metrics
    • resources → import from @opentelemetry/resources
  • feat(sdk-logs): mark @opentelemetry/sdk-logs as stable #7143 @​trentm

... (truncated)

Commits
  • 12a5817 chore: prepare next release (#7213)
  • 2a97587 docs: 3.x migration doc edits (#7216)
  • ebefa76 chore(deps): update dependency eslint to v10.13.0 (#7129)
  • 83b6922 chore(deps): update dependency superagent to v10.4.1 (#7184)
  • 68e9e6e fix(otlp-exporter-base): pick fetch mode from the document origin, not locati...
  • 7d2455e build: lint for unused dependencies with knip (#7200)
  • 5e65e0e fix(core): no longer drop an attribute value that is an object that has `un...
  • 2fbb404 chore(deps): dedupe nx to 23.3.0 (#7205)
  • c971f52 docs(changelog): trim unreleased entries (#7203)
  • 2516215 feat(instrumentation)!: make InstrumentationBase#_enabled protected on both p...
  • Additional commits viewable in compare view

Updates @opentelemetry/resources from 2.10.0 to 2.12.0

Release notes

Sourced from @​opentelemetry/resources's releases.

v2.12.0

2.12.0

🚀 Features

  • chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #7086

🏠 Internal

  • feat(ci): support releasing from maintenance branches #6767 @​pichlermarc
    • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.

v2.11.0

2.11.0

🚀 Features

  • feat(context-async-hooks): implement attach() on AsyncLocalStorageContextManager #6845 @​pichlermarc
    • On Node.js 25.9+, delegates to AsyncLocalStorage.withScope() returning a native RunScope. On older Node.js, falls back to enterWith() with a manual disposable wrapper.
  • feat(sdk-trace): allow configuring the force flush timeout per call #6929 @​LarryHu0217

🐛 Bug Fixes

  • fix(sdk-metrics): ignore Infinity in exponential histograms #7015 @​mwear

🏠 Internal

  • perf(sdk-metrics): reuse a single DataView for exponential histogram bit reads #6998 @​mwear
  • chore(ci): run documentation tests on a weekly schedule #6920 @​LarryHu0217
  • feat(ci): support pre-releases and major version bumps in the release workflow #6768 @​pichlermarc
  • chore(resources): Ensure that multiple uses of serviceInstanceIdDetector.detect() return the same value for service.instance.id
Changelog

Sourced from @​opentelemetry/resources's changelog.

CHANGELOG

All notable changes to this project will be documented in this file.

For API changes, see the API CHANGELOG. For experimental package changes, see the experimental CHANGELOG. For semantic convention package changes, see the semconv CHANGELOG. For notes on migrating to 2.x / 0.200.x see the upgrade guide. For notes on migrating to 3.x see the 3.x migration guide.

Unreleased

💥 Breaking Changes

🚀 Features

  • feat(resources): Deprecate envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetector as stable (the service.instance.id semconv attribute is now stable). #6999 @​trentm

🐛 Bug Fixes

  • fix(core): accept attribute values with shared (non-circular) object references #7068 @​rajanpanth

📚 Documentation

🏠 Internal

3.0.0

💥 Breaking Changes

  • chore(sdk-trace-node)!: remove the @opentelemetry/sdk-trace-node package #7054
    • The sdk-trace-node package has been replaced by the @opentelemetry/sdk-trace package. See the 3.x migration guide for full migration instructions.
  • chore(shim-opentracing)!: remove the @opentelemetry/shim-opentracing package
  • chore(context-async-hooks)!: remove the unused class AsyncHooksContextManager #7078
  • feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
    • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
    • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
    • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
    • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
    • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
    • If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
  • feat(core)!: remove deprecated getTimeOrigin, otperformance, _globalThis, and unrefTimer from @opentelemetry/core #7053

... (truncated)

Commits
  • 92b844e chore: prepare next v2.x release (#7151)
  • a859aff fix(web-common): export getElementXPath utility (#7124)
  • 2bd5a73 chore(web-common)!: deprecate addSpanNetworkEvents() et al instrumentation-...

…with 16 updates

Bumps the production-deps group with 16 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@nestjs/throttler](https://github.com/nestjs/throttler) | `6.5.0` | `6.7.1` |
| [@opentelemetry/api](https://github.com/open-telemetry/opentelemetry-js) | `1.9.1` | `1.10.0` |
| [@opentelemetry/auto-instrumentations-node](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node) | `0.77.0` | `0.82.0` |
| [@opentelemetry/core](https://github.com/open-telemetry/opentelemetry-js) | `2.10.0` | `2.12.0` |
| [@opentelemetry/exporter-trace-otlp-http](https://github.com/open-telemetry/opentelemetry-js) | `0.219.0` | `0.300.0` |
| [@opentelemetry/resources](https://github.com/open-telemetry/opentelemetry-js) | `2.10.0` | `2.12.0` |
| [@opentelemetry/sdk-node](https://github.com/open-telemetry/opentelemetry-js) | `0.219.0` | `0.300.0` |
| [@opentelemetry/semantic-conventions](https://github.com/open-telemetry/opentelemetry-js) | `1.43.0` | `1.44.0` |
| [@prisma/adapter-pg](https://github.com/prisma/orm/tree/HEAD/packages/adapter-pg) | `7.9.1` | `7.10.1` |
| [@prisma/client](https://github.com/prisma/orm/tree/HEAD/packages/client) | `7.9.0` | `7.10.1` |
| [@stellar/stellar-sdk](https://github.com/stellar/js-stellar-sdk) | `17.1.0` | `17.4.0` |
| [axios](https://github.com/axios/axios) | `1.18.1` | `1.21.0` |
| [compression](https://github.com/expressjs/compression) | `1.8.1` | `1.8.2` |
| [express](https://github.com/expressjs/express) | `5.2.1` | `5.3.0` |
| [pg](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg) | `8.22.0` | `8.23.1` |
| [zod](https://github.com/colinhacks/zod) | `4.4.3` | `4.6.7` |



Updates `@nestjs/throttler` from 6.5.0 to 6.7.1
- [Release notes](https://github.com/nestjs/throttler/releases)
- [Changelog](https://github.com/nestjs/throttler/blob/master/CHANGELOG.md)
- [Commits](nestjs/throttler@v6.5.0...v6.7.1)

Updates `@opentelemetry/api` from 1.9.1 to 1.10.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@v1.9.1...v1.10.0)

Updates `@opentelemetry/auto-instrumentations-node` from 0.77.0 to 0.82.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js-contrib/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/packages/auto-instrumentations-node/CHANGELOG.md)
- [Commits](https://github.com/open-telemetry/opentelemetry-js-contrib/commits/auto-instrumentations-node-v0.82.0/packages/auto-instrumentations-node)

Updates `@opentelemetry/core` from 2.10.0 to 2.12.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@v2.10.0...v2.12.0)

Updates `@opentelemetry/exporter-trace-otlp-http` from 0.219.0 to 0.300.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@experimental/v0.219.0...experimental/v0.300.0)

Updates `@opentelemetry/resources` from 2.10.0 to 2.12.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@v2.10.0...v2.12.0)

Updates `@opentelemetry/sdk-node` from 0.219.0 to 0.300.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@experimental/v0.219.0...experimental/v0.300.0)

Updates `@opentelemetry/semantic-conventions` from 1.43.0 to 1.44.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@semconv/v1.43.0...semconv/v1.44.0)

Updates `@prisma/adapter-pg` from 7.9.1 to 7.10.1
- [Release notes](https://github.com/prisma/orm/releases)
- [Commits](https://github.com/prisma/orm/commits/7.10.1/packages/adapter-pg)

Updates `@prisma/client` from 7.9.0 to 7.10.1
- [Release notes](https://github.com/prisma/orm/releases)
- [Commits](https://github.com/prisma/orm/commits/7.10.1/packages/client)

Updates `@stellar/stellar-sdk` from 17.1.0 to 17.4.0
- [Release notes](https://github.com/stellar/js-stellar-sdk/releases)
- [Changelog](https://github.com/stellar/js-stellar-sdk/blob/main/CHANGELOG.md)
- [Commits](stellar/js-stellar-sdk@v17.1.0...v17.4.0)

Updates `axios` from 1.18.1 to 1.21.0
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v1.18.1...v1.21.0)

Updates `compression` from 1.8.1 to 1.8.2
- [Release notes](https://github.com/expressjs/compression/releases)
- [Changelog](https://github.com/expressjs/compression/blob/master/HISTORY.md)
- [Commits](expressjs/compression@v1.8.1...v1.8.2)

Updates `express` from 5.2.1 to 5.3.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@v5.2.1...v5.3.0)

Updates `pg` from 8.22.0 to 8.23.1
- [Changelog](https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md)
- [Commits](https://github.com/brianc/node-postgres/commits/pg@8.23.1/packages/pg)

Updates `zod` from 4.4.3 to 4.6.7
- [Release notes](https://github.com/colinhacks/zod/releases)
- [Commits](colinhacks/zod@v4.4.3...v4.6.7)

---
updated-dependencies:
- dependency-name: "@nestjs/throttler"
  dependency-version: 6.7.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/api"
  dependency-version: 1.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/auto-instrumentations-node"
  dependency-version: 0.82.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/core"
  dependency-version: 2.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/exporter-trace-otlp-http"
  dependency-version: 0.300.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/resources"
  dependency-version: 2.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/sdk-node"
  dependency-version: 0.300.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@opentelemetry/semantic-conventions"
  dependency-version: 1.44.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@prisma/adapter-pg"
  dependency-version: 7.10.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@prisma/client"
  dependency-version: 7.10.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: "@stellar/stellar-sdk"
  dependency-version: 17.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: axios
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: compression
  dependency-version: 1.8.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-deps
- dependency-name: express
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: pg
  dependency-version: 8.23.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
- dependency-name: zod
  dependency-version: 4.6.7
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot requested a review from Omoboi-dev as a code owner November 2, 2026 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants