Skip to content

chore(deps): bump the production-dependencies group with 8 updates - #76

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-366f0a65e7
Closed

chore(deps): bump the production-dependencies group with 8 updates#76
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-366f0a65e7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 8 updates:

Package From To
@aws-sdk/client-s3 3.1149.0 3.1156.0
@graphql-tools/schema 10.1.3 10.1.5
@opentelemetry/api 1.9.1 1.10.0
@opentelemetry/auto-instrumentations-node 0.81.0 0.82.0
@opentelemetry/exporter-trace-otlp-http 0.223.0 0.300.0
@opentelemetry/sdk-node 0.223.0 0.300.0
graphql-yoga 5.24.4 5.24.6
multer 2.4.0 2.5.0

Updates @aws-sdk/client-s3 from 3.1149.0 to 3.1156.0

Release notes

Sourced from @​aws-sdk/client-s3's releases.

v3.1156.0

3.1156.0(2026-10-22)

Documentation Changes
  • client-lambda: AWS Lambda durable functions now supports payloads up to 1 MB for checkpoints, callback completion, and error details. (cdd6c609)
New Features
  • clients: update client endpoints as of 2026-10-22 (e5cd1562)
  • client-opensearchserverless: Adds APIs to create, get, list, and cancel ingestion jobs, and to create, get, list, and delete ingestion streams, for ingesting data from Amazon S3 into OpenSearch Serverless collections. (7712bce0)
  • client-continuum: Releasing Continuum for Code Vulnerabilities APIs for SDKs (0cbbd64c)
  • client-connect: Adds support for customer queryable replication errors. (4507ef01)
  • client-ec2: AWS Transit Gateway now provides managed one-to-one NAT directly on its attachments, through integration with Regional Private NAT Gateway. Use ModifyTransitGatewayAttachmentNatConfiguration to enable NAT and configure NAT rules, and GetTransitGatewayAttachmentNatConfiguration to view them. (68bea2ce)
  • client-bedrock-agentcore: Adds the dimension name to evaluation results and batch evaluation summaries. For multi-dimensional LLM-as-a-Judge evaluators, each result and summary now identifies which dimension it corresponds to. (185f264b)
  • client-networkmanager: AWS Cloud WAN now provides managed one-to-one NAT directly on it's core network attachments, through integration with Regional Private NAT Gateway. Use UpdateAttachmentNatConfiguration to enable NAT and configure NAT rules, and ListAttachmentNatConfigurations to view them. (944335d4)
  • client-bedrock-agentcore-control: Adds model-based routing and fallback to AgentCore Gateway rules. Rules can match the requested model, route to a specific model, and fall back across inference targets with an optional circuit breaker. Adds multi-dimensional rating scales for AgentCore Evaluations LLM-as-a-Judge evaluators. (9c2b09c2)
  • client-elementalinference: Elemental Inference now supports feed scheduling, letting you apply feed configuration changes at a time you choose instead of building your own automation. (b4108829)
  • client-glue: Add support for large worker types in AWS Glue (89ac4073)
  • client-kafkaconnect: Amazon MSK Connect now supports pausing and resuming connectors via the asynchronous PauseConnector and ResumeConnector APIs. Paused connectors keep their configuration and committed offsets and resume where they left off. Each call returns an operation ARN to track with DescribeConnectorOperation. (f5a4343a)
  • client-ivs-realtime: Adds RevokeConnectionToken operation for Amazon IVS Real-Time Streaming. (7c85a26a)

For list of updated packages, view updated-packages.md in assets-3.1156.0.zip

v3.1155.0

3.1155.0(2026-10-21)

Chores
  • temporarily disconnect from eclipse for Java formatting (#8375) (6d14aac7)
  • codegen: sync for JSON string serializer buffer fix and retryMode docs link (#8373) (5f53137d)
  • finspace: Remove finspace and finspace-data clients following the service shutdown (#8369) (48e34c48)
  • tnb: Remove tnb clients following shutdown (#8370) (e37bf8c2)
New Features
  • client-quicksight: Adds support for SharePoint and OneDrive two-legged OAuth certificate credentials and Google Workspace service account credentials when creating data sources (d0d47ac9)
  • client-sfn: Release minor updates to API model (6bb8593f)
  • client-network-firewall: Adds support for Network Firewall Resolved IP validation. (6a634360)
  • client-datazone: Added custom designations support with new CRUD APIs. The designation field in project membership and policy grant APIs supports a new enum for custom designations. These APIs also support a new field for custom designation id. (10021565)
  • client-ec2: Adds new response fields to DescribeInstanceStatus and Network Insights analysis results. (8e379695)
  • client-lightsail: This release adds support for metrics related to system-disk performance. (d21dd9d9)
  • client-healthlake: Update the UpdateProfileWithAgent API to return a streaming response to provide more frequent updates on what the agent is doing. (c2730b30)
  • client-polly: Added support for the new voices - Kenneth (en-US), Nate (en-US), Tina (de-DE), Carlos (es-US), Carolina (pt-BR), Leo (pt-BR), Curtis (en-AU), Kiara (en-IN), Arjun (en-IN) and Hyunduk (ko-KR). They are available as a Generative voices only. (4494f473)
  • client-connect: Added support for AWS-managed security profiles. (04f0c0b5)
  • client-auto-scaling: EC2 Auto Scaling now supports account settings, letting you manage account-level configuration for Auto Scaling. (d0cdb396)
  • client-lex-models-v2: Adds support for Assisted NLU - Dialog Manager mode allowing usage of LLMs as the default NLU system and dialog management (671f2125)

... (truncated)

Changelog

Sourced from @​aws-sdk/client-s3's changelog.

3.1156.0 (2026-10-22)

Note: Version bump only for package @​aws-sdk/client-s3

3.1155.0 (2026-10-21)

Note: Version bump only for package @​aws-sdk/client-s3

3.1154.0 (2026-10-20)

Note: Version bump only for package @​aws-sdk/client-s3

3.1153.0 (2026-10-19)

Note: Version bump only for package @​aws-sdk/client-s3

3.1152.0 (2026-10-14)

Note: Version bump only for package @​aws-sdk/client-s3

3.1151.0 (2026-10-13)

Note: Version bump only for package @​aws-sdk/client-s3

3.1150.0 (2026-10-12)

... (truncated)

Commits

Updates @graphql-tools/schema from 10.1.3 to 10.1.5

Changelog

Sourced from @​graphql-tools/schema's changelog.

10.1.5

Patch Changes

  • #8445 82457d1 Thanks @​ardatan! - dependencies updates:

  • #8445 82457d1 Thanks @​ardatan! - Fix: Preserve symbol-keyed GraphQL extensions when building, merging, or extracting schemas.

    GraphQL.js v17 allows string | symbol keys on schema/type/field extensions (via toObjMapWithSymbols). @graphql-tools was dropping those symbol keys in two places:

    1. mergeDeep only walked enumerable string keys (for...in), so symbol extensions were lost when applying schemaExtensions.
    2. extractExtensionsFromSchema did not copy non-enumerable own symbol keys (enumerable symbols already survive object rest/spread; the explicit loop covers the non-enumerable case).

    Example (bug)

    import { makeExecutableSchema } from '@graphql-tools/schema'
const META = Symbol('META')
const schema = makeExecutableSchema({
typeDefs: /* GraphQL */ type Query { hello: String },
schemaExtensions: {
schemaExtensions: {
[META]: { source: 'app' },
tagged: true,
},
types: {},
},
})
// Before: only string keys survived
// schema.extensions === { tagged: true }
// After: symbol keys are preserved
// schema.extensions[META] === { source: 'app' }
// schema.extensions.tagged === true

    Schema extension merge/extract and resolver merging always enable { enumerable: true, nonEnumerable: true } so symbol keys survive in tools' own merge/extract paths on every supported GraphQL.js major. (GraphQL.js itself may still drop symbol keys from field configs below v17 when rebuilding types.)

    mergeDeep API

    mergeDeep now accepts an options object. The old positional boolean arguments still work but are deprecated.

... (truncated)

Commits

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.81.0 to 0.82.0

Release notes

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

auto-instrumentations-node: v0.82.0

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

... (truncated)

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/exporter-trace-otlp-http from 0.223.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/sdk-node from 0.223.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/sdk-node'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

@dependabot
chore(deps): bump the production-dependencies group with 8 updates
a2eb76d 
Bumps the production-dependencies group with 8 updates:

| Package | From | To |
| --- | --- | --- |
| [@aws-sdk/client-s3](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3) | `3.1149.0` | `3.1156.0` |
| [@graphql-tools/schema](https://github.com/ardatan/graphql-tools/tree/HEAD/packages/schema) | `10.1.3` | `10.1.5` |
| [@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.81.0` | `0.82.0` |
| [@opentelemetry/exporter-trace-otlp-http](https://github.com/open-telemetry/opentelemetry-js) | `0.223.0` | `0.300.0` |
| [@opentelemetry/sdk-node](https://github.com/open-telemetry/opentelemetry-js) | `0.223.0` | `0.300.0` |
| [graphql-yoga](https://github.com/graphql-hive/graphql-yoga/tree/HEAD/packages/graphql-yoga) | `5.24.4` | `5.24.6` |
| [multer](https://github.com/expressjs/multer) | `2.4.0` | `2.5.0` |


Updates `@aws-sdk/client-s3` from 3.1149.0 to 3.1156.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-s3/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1156.0/clients/client-s3)

Updates `@graphql-tools/schema` from 10.1.3 to 10.1.5
- [Release notes](https://github.com/ardatan/graphql-tools/releases)
- [Changelog](https://github.com/ardatan/graphql-tools/blob/master/packages/schema/CHANGELOG.md)
- [Commits](https://github.com/ardatan/graphql-tools/commits/@graphql-tools/schema@10.1.5/packages/schema)

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.81.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/exporter-trace-otlp-http` from 0.223.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.223.0...experimental/v0.300.0)

Updates `@opentelemetry/sdk-node` from 0.223.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.223.0...experimental/v0.300.0)

Updates `graphql-yoga` from 5.24.4 to 5.24.6
- [Release notes](https://github.com/graphql-hive/graphql-yoga/releases)
- [Changelog](https://github.com/graphql-hive/graphql-yoga/blob/main/packages/graphql-yoga/CHANGELOG.md)
- [Commits](https://github.com/graphql-hive/graphql-yoga/commits/graphql-yoga@5.24.6/packages/graphql-yoga)

Updates `multer` from 2.4.0 to 2.5.0
- [Release notes](https://github.com/expressjs/multer/releases)
- [Changelog](https://github.com/expressjs/multer/blob/main/CHANGELOG.md)
- [Commits](expressjs/multer@v2.4.0...v2.5.0)

---
updated-dependencies:
- dependency-name: "@aws-sdk/client-s3"
  dependency-version: 3.1156.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@graphql-tools/schema"
  dependency-version: 10.1.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@opentelemetry/api"
  dependency-version: 1.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@opentelemetry/auto-instrumentations-node"
  dependency-version: 0.82.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- 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-dependencies
- dependency-name: "@opentelemetry/sdk-node"
  dependency-version: 0.300.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: graphql-yoga
  dependency-version: 5.24.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: multer
  dependency-version: 2.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 26, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 2, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/production-dependencies-366f0a65e7 branch November 2, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants