[dependabot]

Bumps the backend-minor-patch group in /Servers with 18 updates:

Package	From	To
@ai-sdk/anthropic	4.0.94	4.0.97
@ai-sdk/openai	4.0.106	4.0.109
@aws-sdk/client-ses	3.1161.0	3.1163.0
@azure/msal-node	7.1.2	7.2.0
@daytonaio/sdk	0.227.0	0.230.0
@e2b/code-interpreter	2.9.0	2.9.1
@opentelemetry/exporter-logs-otlp-http	0.300.0	0.301.0
@opentelemetry/exporter-metrics-otlp-http	0.300.0	0.301.0
@opentelemetry/resources	3.0.0	3.1.0
@opentelemetry/sdk-logs	3.0.0	3.1.0
@opentelemetry/sdk-metrics	3.0.0	3.1.0
@smithy/node-http-handler	4.14.1	4.14.2
ai	7.0.159	7.0.163
bullmq	6.5.3	6.7.0
docx	9.15.1	9.15.2
express-rate-limit	8.7.2	8.7.3
google-auth-library	11.3.2	11.3.3
playwright	1.64.1	1.65.0

Updates @ai-sdk/anthropic from 4.0.94 to 4.0.97

Changelog

Sourced from @​ai-sdk/anthropic's changelog.

4.0.97

Patch Changes

• fd7e8a7: Preserve the order of text and complete function calls in streamed Google responses, including standalone thought signatures on empty text or reasoning parts.

  Keep provider metadata on empty text parts when converting results to response messages so it can be passed back in subsequent requests.

  Omit foreign-provider empty signature text when replaying history through Anthropic or Bedrock, preserving Bedrock’s existing native reasoning-history handling.

• 8291ccf: Add MiniMax serviceTier support for standard and priority admission. Omit tiers belonging to another known provider with an unsupported-setting warning instead of forwarding incompatible values. Expose the applied serviceTier, when returned, in Anthropic-compatible generation, stream and batch metadata without changing existing metadata construction types.

• 9754014: Add typed streaming heartbeat parts. Anthropic emits them only with includePings: true (disabled by default), without requiring raw chunks. Core forwards pings through stream retries without storing them as generated content or sending them to UI message streams. Consumers with exhaustive stream-part switches must handle the new ping union variant when upgrading, even when the opt-in is disabled. Typed pings do not flush partial words during stream smoothing.

• 4b8f00e: Add a supportsNativeStructuredOutput opt-in to the Vertex Anthropic provider so auto can use native structured output for Claude 4.5 and newer when enabled by Google Cloud policy. Keep tool emulation as the default and avoid adding the structured-output beta header for providers without strict tool support.

• 8b11ff6: Support deleting files, retrieving metadata, and streaming downloads of generated files through the Anthropic Files API. Metadata reads and uploads expose consistent media type, size, creation time, expiration, and provider metadata when available. Downloads preserve Anthropic’s restriction to files generated by tools or skills.

• Updated dependencies [36802d4]

• Updated dependencies [e0143b0]

• Updated dependencies [934100c]

• Updated dependencies [892af4d]

• Updated dependencies [89aff56]

• Updated dependencies [41465fd]

• Updated dependencies [9754014]

• Updated dependencies [4bb73b0]

• Updated dependencies [2e44144]

  • @​ai-sdk/provider@​4.0.36
  • @​ai-sdk/provider-utils@​5.0.75

4.0.96

Patch Changes

• Updated dependencies [fa15312]
  • @​ai-sdk/provider-utils@​5.0.74

4.0.95

Patch Changes

• 2cd0a97: Enable native structured output and strict tools for supported Claude 5 models on Bedrock. In automatic mode, Bedrock and Anthropic now fall back for schemas that native structured output cannot represent: recursive references, open objects, or more than ten optional properties. Anthropic uses the JSON response tool; Bedrock Converse uses the JSON tool or JSON instructions for models that reject forced tool use. The JSON-tool fallback excludes disabled and unselected application tools. Explicit outputFormat selection remains unchanged.
• 4ae6986: fix(anthropic): parse valid JSON string tool input and safely serialize BigInt and cycles in tool results
• Updated dependencies [51ca5b7]
• Updated dependencies [dc6f1c3]
• Updated dependencies [4ae6986]
  • @​ai-sdk/provider-utils@​5.0.73

Commits

• bdc3f91 Version Packages (#24424)
• 9754014 feat(anthropic): forward streaming ping events by introducing new stream part...
• 4b8f00e feat(google-vertex): add Anthropic native structured output opt-in (#23862)
• 8291ccf feat(anthropic,minimax): support MiniMax tiers and applied-tier metadata (#19...
• 8b11ff6 feat(anthropic): add FilesV4 support for file operations (#21521)
• fd7e8a7 fix(google): preserve streamed tool ordering and signature history (#24349)
• 2feaeec Version Packages (#24410)
• 7498799 Version Packages (#24380)
• 4ae6986 fix(providers): preserve valid JSON tool arguments and serialize result graph...
• 2cd0a97 fix(amazon-bedrock): enable Claude 5 structured outputs with schema fallbacks...
• See full diff in compare view

Updates @ai-sdk/openai from 4.0.106 to 4.0.109

Changelog

Sourced from @​ai-sdk/openai's changelog.

4.0.109

Patch Changes

• 27528db: Expose customTool through azure.tools for Azure Responses models, sharing the OpenAI custom tool factory and its raw string input support.

• 7bb309d: add memoryLimit and networkPolicy properties in codeInterpreter tool

• 7a90522: Add Secure MCP tunnel support to the OpenAI MCP tool via tunnelId. Tunnel targets cannot be combined with serverUrl or connectorId; existing URL and connector configurations remain compatible.

• 6549344: feat(openai): support GPT Image 2.6 models with complexity, markup-guided edits (markup), animated GIF output (outputFormat: 'gif', frameCount, frameDurationMs), and safetyIdentifier for image models

• 5f9bb8e: feat (provider/openai): forward the moderation option to /images/edits

• 934100c: Report the actual OpenAI Chat HTTP endpoint (also used by Azure Chat and Bedrock Mantle Chat) through optional request metadata and model-call end events. Record its host and port on OpenTelemetry chat spans without exposing URL credentials, paths, queries, or fragments. Expose only the sanitized HTTP origin in text and object generation results and step/finish callbacks. Providers that do not report an endpoint leave these attributes unset.

• 892af4d: feat (provider/openai): implement server-side realtime extensions

  OpenAIRealtimeModel now implements getServerWebSocketConfig(), returning the upstream realtime WebSocket URL for conversation and transcription intents plus header auth derived from the model's configured credentials. Dedicated transcription sessions serialize with session.type: "transcription" and the selected realtime model id. Translation is rejected until the normalized realtime codec supports its distinct wire protocol. The event mapper now populates normalized usage on response-done and input-transcription-completed (gross input/output token counts with cached portions reported separately; duration usage for duration-billed transcription).

  Transcription serialization honors the explicit transcription model and rejects unsupported output settings. Gross token totals and reported modality/cache counts are retained; duration uses seconds. OpenAI Live retains its existing connection API and rejects unsupported intents.

• 243bf22: Forward per-message providerOptions.openai.name on Chat Completions system, developer, user, and assistant messages. Validate names as strings and warn when configured on unsupported tool messages.

• 5cc6d28: Expose azure.tools.shell for local and hosted shell execution through the Azure Responses API.

• 41465fd: Expose optional transcription word timings separately from segments and accept shared timestampGranularities. Explicit provider timing settings take precedence. OpenAI now sends timestamp_granularities only with verbose_json and warns when a requested timing is unavailable or excluded.

• Updated dependencies [36802d4]

• Updated dependencies [e0143b0]

• Updated dependencies [934100c]

• Updated dependencies [892af4d]

• Updated dependencies [89aff56]

• Updated dependencies [41465fd]

• Updated dependencies [9754014]

• Updated dependencies [4bb73b0]

• Updated dependencies [2e44144]

  • @​ai-sdk/provider@​4.0.36
  • @​ai-sdk/provider-utils@​5.0.75

4.0.108

Patch Changes

• Updated dependencies [fa15312]
  • @​ai-sdk/provider-utils@​5.0.74

4.0.107

Patch Changes

• 4ae6986: fix(openai): preserve valid JSON string tool arguments and serialize BigInt and cycles in tool calls and results, retaining malformed argument replay fallbacks
• 226b7da: Forward languages and keywords transcription hints as repeated multipart fields instead of silently dropping them. Warn when these REST-only options are supplied to streaming transcription.
• Updated dependencies [51ca5b7]
• Updated dependencies [dc6f1c3]
• Updated dependencies [4ae6986]
  • @​ai-sdk/provider-utils@​5.0.73

Commits

• bdc3f91 Version Packages (#24424)
• 6549344 feat(openai): support GPT Image 2.6 models and image options (#24560)
• 892af4d feat (provider): server-side realtime extensions for RealtimeModelV4 (#16137)
• 5cc6d28 feat(provider/azure): add shell in azure Responses tools (#12959)
• 41465fd feat(ai): expose transcription word timings separately from segments (#23543)
• 243bf22 feat(openai): support Chat Completions message names (#11020)
• 7a90522 feat(openai): support Secure MCP tunnels (#17929)
• 27528db feat(provider/azure): custom tool in azure Responses tools (#12964)
• 7bb309d feat(provider/openai): add memoryLimit and networkPolicy in `codeInterpre...
• 5f9bb8e feat (provider/openai): forward the moderation option to /images/edits (#20745)
• Additional commits viewable in compare view

Updates @aws-sdk/client-ses from 3.1161.0 to 3.1163.0

Release notes

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

v3.1163.0

3.1163.0(2026-11-05)

New Features

• clients: update client endpoints as of 2026-11-05 (57e9f143)
• client-bedrock-agentcore-control: Adds support for OAuth2 Authorization Server Metadata (RFC 8414) discovery URLs in custom JWT authorizer and OAuth2 credential provider configurations. (950c852a)
• client-sagemaker: Fixed the ImageDeleted and ImageVersionDeleted waiters to succeed on the ResourceNotFound error returned by DescribeImage and DescribeImageVersion (6cc77117)
• client-wafv2: AWS WAF customers who monetize AI traffic on Web ACLs can now configure payments through connected accounts (Stripe). (9e7dd06f)
• client-appintegrations: This release adds a LastModifiedRegion field to GetApplication and ListApplications so customers can see which Region an application was last modified in. (878faafe)
• client-quicksight: Amazon QuickSight adds APIs to view account service role settings and switch to or replace a customer-managed IAM role. (98371e60)
• client-lambda-microvms: AWS Lambda MicroVMs now support the x86-64 CPU architecture, which you can select in addition to ARM64 (Graviton) when launching a MicroVM. (928e07cc)
• client-bedrock-agent-runtime: Amazon Bedrock Managed Knowledge Base now supports an optional mediaId parameter in GetDocumentContent that you can use to retrieve images embedded in source documents. (0740a76b)
• client-securityagent: Adds support for IAM Identity Center groups as Agent Space members. CreateMembership, DeleteMembership, and ListMemberships now accept the GROUP member type. ListMemberships can filter by USER, GROUP, or ALL, and returns group display name and description. (a8e028e7)
• client-cloudwatch-logs: Adds account-level retention policies with dry run preview and the Essentials log group class to Amazon CloudWatch Logs (da8a2a29)
• client-datasync: Adds support for federated identity on Azure Blob Storage and object storage locations, enabling DataSync to authenticate to Azure and Google Cloud Storage using Workload Identity Federation (WIF) over OpenID Connect (OIDC) instead of stored long-lived credentials. (9a8be11b)
• client-route-53-domains: Route 53 Domains now supports restoring domains. This release adds the RestoreDomain API to self-serve domain restoration. (ce3d5a2c)
• client-glue: AWS Glue Spark ETL jobs can now auto-upgrade to the latest version. Set GlueVersion to Auto, then track progress with the AutoVersionStatus field in GetJob. Use StartJobUpgradeAnalysis to approve or decline an upgrade, GetJobUpgradeAnalysis to view details, and StopJobUpgradeAnalysis to stop it. (b04dd0b0)
• client-account-access-runtime: Adds SDK support for Account Access user portal operations, enabling users to list out and get credentials for role assignments configured in AWS IAM Account Access Manager. (0372bae5)
• client-qconnect: Adds support for real-time agent assistance and self-service with Amazon Connect Global Resiliency, including cross-Region replication of supported AI agent resources and configurations. (d3305fbd)
• client-agent-registry-control: Adds support for OAuth2 Authorization Server Metadata (RFC 8414) discovery URLs in custom JWT authorizer. (0b9b8f4d)

Bug Fixes

• snapshot-testing: add camelCase checksumAlgorithm to customFields (#8403) (0bde7a79)

---

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

v3.1162.0

3.1162.0(2026-11-04)

Documentation Changes

• fix typos in credential-providers and xhr-http-handler READMEs (#8400) (13b91575)

New Features

• clients: update client endpoints as of 2026-11-04 (7b30cd35)
• client-lookoutequipment: Amazon Lookout for Equipment reached end of support on October 7, 2026. All Lookout for Equipment APIs are now marked as deprecated. (9a4a6882)
• client-rolesanywhere: Adds the crlDpRevocationEnabled field to enable automatic revocation checking using CRL distribution points in X.509 certificates. (5c3071ce)
• client-marketplace-discovery: GetListing and SearchListings APIs now return G2 and PeerSpot review sources in review summaries. (cb49279d)
• client-ec2: Add the Unsupported SupportabilityScore to GetCapacityManagerSupportabilityScores. (e8a84dc8)
• client-elastic-beanstalk: Adds DefaultAmiList to DescribePlatformVersion to return the default AMI for each processor architecture that a platform version supports. (a7dfafce)
• client-iotsitewise: Adds support for an optional jobName on CreateDatasetExportJob. The jobName is returned by DescribeDatasetExportJob and ListDatasetExportJobs, making dataset export jobs easier to identify and track. If jobName is omitted, a default name is generated automatically. (33a8bf05)
• client-connect-contact-lens: Rules TBAC GA (Contact Lens V1) - Adds an optional ListFilter (CategoriesAttributeFilter with OrConditions, AndCondition and TagCondition) to ListRealtimeContactAnalysisSegments. This filters matched categories by rule tags. It also adds an optional RuleId to CategoryDetails in the response. (c09702f1)
• client-taxsettings: Adds Colombia additional information (responsibility codes, taxpayer type code, and RUT issue date) and a rejection reason (statusReason) to tax registration responses, and adds Argentina and Uruguay tax registration types. (582f0ce2)
• client-s3tables: Amazon S3 Tables now supports migrating AWS Glue Data Catalog tables into S3 Table buckets. This release adds the StartTableMigration, SyncTableMigration, UpdateTableMigration, CompleteTableMigration, GetTableMigration, and ListTableMigrations APIs. (235b2d68)

... (truncated)

Changelog

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

3.1163.0 (2026-11-05)

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

3.1162.0 (2026-11-04)

Features

• codegen: add a default socket timeout per service (#8396) (8f62478)

Commits

• 9163d15 Publish v3.1163.0
• 80cb789 Publish v3.1162.0
• 8f62478 feat(codegen): add a default socket timeout per service (#8396)
• See full diff in compare view

Updates @azure/msal-node from 7.1.2 to 7.2.0

Release notes

Sourced from @​azure/msal-node's releases.

@​azure/msal-node v7.2.0

7.2.0

Thu, 05 Nov 2026 01:03:50 GMT

Minor changes

• Bump @​azure/msal-common to v16.16.0 (beachball)

Patches

• Bind interactive browser authorization responses to per-request state #8952 (undefined)

Commits

• a8a8141 Upgrade compatible dependencies to address security advisories (#8965)
• fd18de7 AB#3715428: WI-2 Implement WAM DPoP routing outcome handling and cache policy...
• e554958 Fix device-code approval prompt handling in E2E tests (#8964)
• 32368ef Document Markdown link rules for Git submodule boundaries (#8922)
• 306f818 Bind interactive browser authorization responses to per-request state (#8952)
• 6d1e176 build(deps): bump benchmark-action/github-action-benchmark from 1.22.1 to 1.2...
• ee1fa0f Add weekly npm updates with a seven-day cooldown (#8949)
• c432013 build(deps-dev): bump electron from 42.11.4 to 42.11.18 (#8950)
• 83edb9d KMSI broker E2E corrections and NAA coverage (2 PBIs) (#8924)
• 11bbd90 build(deps): bump ip-address from 10.7.3 to 10.7.5 in /samples/e2eTestUtils (...
• Additional commits viewable in compare view

Updates @daytonaio/sdk from 0.227.0 to 0.230.0

Release notes

Sourced from @​daytonaio/sdk's releases.

v0.230.0

0.230.0 (2026-11-05)

Chores

• sync go.sum for v0.227.2 (#445)
• sync release/v0 with main (#457)
• deps: batch dependabot updates for release/v0 2026-11-05 (#497, #490)
• sdk-go: bump to v0.230.0 (#505)

❤️ Thank You

• daytonaBot
• Mirko Džaja @​MDzaja

v0.227.3

0.227.3 (2026-11-02)

Chores

• sdk-go: bump to v0.227.3 (#447)

❤️ Thank You

• daytonaBot

v0.227.2

0.227.2 (2026-11-02)

🩹 Fixes

• sdk-ruby: take a timeout in create() and name the sandbox when it runs out (#428)

Chores

• sync go.sum for v0.227.0 (#429)
• ci: prepare release/v0 to ship the 0.x CLI as daytona-v0 after the 2.x cutover (#433)
• deps: sync poetry.lock marker order with poetry lock (#435)
• sdk-go: bump to v0.227.1 (#443)
• sdk-go: bump to v0.227.2 (#444)

❤️ Thank You

• Aibek Izhanov @​izhanov
• daytonaBot
• Mirko Džaja @​MDzaja

v0.227.1

0.227.1 (2026-11-02)

... (truncated)

Commits

• 8006f63 chore(sdk-go): bump to v0.230.0 (#505)
• ff644e3 chore(deps): batch dependabot updates for release/v0 2026-11-05 (#497)
• 9f6dbae ci(release): update the daytona Homebrew formula from 0.x until 2.x is stable...
• 3f2cf7c docs(v0): describe release/v0 as the 0.x line and retarget its main-only work...
• f85c0d0 ci(secret-scan): add gitleaks secret scanning to release/v0 (#466)
• 25208d5 ci(release): need one release environment approval per publish and release ru...
• 08d9fef chore: sync release/v0 with main (#457)
• 6ee8108 chore: sync go.sum for v0.227.2 (#445)
• 6db8619 chore(sdk-go): bump to v0.227.2 (#444)
• a057433 chore(sdk-go): bump to v0.227.1 (#443)
• Additional commits viewable in compare view

Updates @e2b/code-interpreter from 2.9.0 to 2.9.1

Changelog

Sourced from @​e2b/code-interpreter's changelog.

2.9.1

Patch Changes

• 8cc9ed1: Document that logs.stdout, logs.stderr and OutputMessage.line hold raw chunks with newlines kept (join them with '' to rebuild the output), and that Result.png, Result.jpeg and Result.pdf are base64-encoded.
• 7d10433: Fix readLines quadratic line reassembly when streaming long single-line outputs (e.g. base64 images, wide DataFrames, large JSON): decode and scan only each new chunk, accumulating line fragments in an array that is joined once per emitted line, instead of appending to and re-scanning a single string buffer on every chunk.
• ac0727b: Fix OutputMessage.timestamp in the JS Code Interpreter to use the backend timestamp (Unix epoch in nanoseconds) sent with each stdout/stderr message, instead of the client clock (new Date().getTime() * 1000). The type is unchanged (number); this aligns the value with the documented contract and the Python SDK. Because nanosecond epoch values exceed Number.MAX_SAFE_INTEGER, the JS value is precise to a few hundred nanoseconds (documented on OutputMessage.timestamp).
• Updated dependencies [320f39d]
• Updated dependencies [36258c1]
• Updated dependencies [8e37561]
  • e2b@2.62.1

Commits

• fd72526 [skip ci] Release new versions
• 6c349d9 chore(deps): drop unused devDependencies and migrate to @​cloudflare/vitest-pl...
• ac0727b fix(code-interpreter): use backend timestamp in JS OutputMessage (#2077)
• 8cc9ed1 docs(code-interpreter): document result formats and output chunks (#2066)
• 7d10433 fix(code-interpreter-js): make readLines linear on long single-line outputs (...
• 5733399 fix(deps): resolve zod to ^4.6.6 for GHSA-mrhx-c7xc-m3w5 (high) (#2029)
• See full diff in compare view

Updates @opentelemetry/exporter-logs-otlp-http from 0.300.0 to 0.301.0

Release notes

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

experimental/v0.301.0

0.301.0

💥 Breaking Changes

• feat(sdk-node)!: The experimental startNodeSdk() code path for environment-based config (i.e. when not using a config file), has full option coverage. #6999 @​trentm
  • startNodeSdk() should now be a viable replacement for new NodeSDK(), supporting similar (but not exactly the same) options for configuring most SDK components.
  • startNodeSDK() has been deprecated, use startNodeSdk() (slight capitalization change).
  • Two resource detectors have been added to the default set for new NodeSDK() users: os and serviceinstance. This means that when not specifying OTEL_NODE_RESOURCE_DETECTORS, the SDK Resource will include os.* and service.instance.id attributes.
• refactor(configuration)!: The responsibility of the configuration package has been reduced to just the parsing, validation, and TypeScript types for declarative config files. #6999 @​trentm
  • Breaking: The configuration package no longer supports creating a synthetic ConfigurationModel from environment variables.
  • Breaking: The configuration package API has changed: createConfigFactory() has been replaced with `parseConfigFile().

🐛 Bug Fixes

• fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (#7261) @​avens19
• fix(otlp-grpc-exporter-base): avoid an incomplete mTLS warning for root-CA-only TLS configuration (#7235) @​LarryHu0217
• fix(sdk-node): warn and skip, instead of erroring, on an unknown resource detector name in declarative config #7252 @​trentm
• fix(sdk-node): use OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT environment variables for span limits #6999 @​trentm
  • Before this change, different environment variable names (see next point), that are not in the OTel spec were used. They will still be supported as a fallback for the spec names for a period of approximately six months.
  • The OTEL_SPAN_ATTRIBUTE_PER_EVENT_COUNT_LIMIT and OTEL_SPAN_ATTRIBUTE_PER_LINK_COUNT_LIMIT environment variables are deprecated. Support for them will be removed sometime after six months, to allow transition to the correct environment variables in the spec.
• fix(otlp-exporter-base): pick the browser fetch mode from the document origin, so exports from an opaque-origin document (e.g. a sandboxed iframe) no longer fail with mode: 'same-origin' #7211 @​MO2k4
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.

📚 Documentation

• docs(exporters): update dead semantic conventions resource specification links in OTLP exporters #7254 @​helmipradita

Commits

• 9985264 chore: prepare next release (#7272)
• 7983f1c fix: raise @​opentelemetry/api peer floor to 1.10.0 where needed (#7259)
• 0a5c4ed chore(deps): update dependency lerna to v10.1.1 (#7270)
• 4eda691 fix(propagator-b3): reject invalid trace id lengths (#7262)
• 5ca48a7 fix(context-zone): declare the @​opentelemetry/api peer dependency (#7268)
• babaf15 docs(migration): note that API 1.10.0 needs SDK 3.x (#7253)
• daae704 fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (...
• cc2a315 fix(otlp-grpc-exporter-base): avoid false mTLS configuration warnings (#7241)
• 29eec06 fix(sdk-node): warn and skip, instead of erroring, on an unknown resource det...
• 4667c0a docs: update dead semantic conventions resource specification links (#7254)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-metrics-otlp-http from 0.300.0 to 0.301.0

Release notes

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

experimental/v0.301.0

0.301.0

💥 Breaking Changes

• feat(sdk-node)!: The experimental startNodeSdk() code path for environment-based config (i.e. when not using a config file), has full option coverage. #6999 @​trentm
  • startNodeSdk() should now be a viable replacement for new NodeSDK(), supporting similar (but not exactly the same) options for configuring most SDK components.
  • startNodeSDK() has been deprecated, use startNodeSdk() (slight capitalization change).
  • Two resource detectors have been added to the default set for new NodeSDK() users: os and serviceinstance. This means that when not specifying OTEL_NODE_RESOURCE_DETECTORS, the SDK Resource will include os.* and service.instance.id attributes.
• refactor(configuration)!: The responsibility of the configuration package has been reduced to just the parsing, validation, and TypeScript types for declarative config files. #6999 @​trentm
  • Breaking: The configuration package no longer supports creating a synthetic ConfigurationModel from environment variables.
  • Breaking: The configuration package API has changed: createConfigFactory() has been replaced with `parseConfigFile().

🐛 Bug Fixes

• fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (#7261) @​avens19
• fix(otlp-grpc-exporter-base): avoid an incomplete mTLS warning for root-CA-only TLS configuration (#7235) @​LarryHu0217
• fix(sdk-node): warn and skip, instead of erroring, on an unknown resource detector name in declarative config #7252 @​trentm
• fix(sdk-node): use OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT environment variables for span limits #6999 @​trentm
  • Before this change, different environment variable names (see next point), that are not in the OTel spec were used. They will still be supported as a fallback for the spec names for a period of approximately six months.
  • The OTEL_SPAN_ATTRIBUTE_PER_EVENT_COUNT_LIMIT and OTEL_SPAN_ATTRIBUTE_PER_LINK_COUNT_LIMIT environment variables are deprecated. Support for them will be removed sometime after six months, to allow transition to the correct environment variables in the spec.
• fix(otlp-exporter-base): pick the browser fetch mode from the document origin, so exports from an opaque-origin document (e.g. a sandboxed iframe) no longer fail with mode: 'same-origin' #7211 @​MO2k4
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.

📚 Documentation

• docs(exporters): update dead semantic conventions resource specification links in OTLP exporters #7254 @​helmipradita

Commits

• 9985264 chore: prepare next release (#7272)
• 7983f1c fix: raise @​opentelemetry/api peer floor to 1.10.0 where needed (#7259)
• 0a5c4ed chore(deps): update dependency lerna to v10.1.1 (#7270)
• 4eda691 fix(propagator-b3): reject invalid trace id lengths (#7262)
• 5ca48a7 fix(context-zone): declare the @​opentelemetry/api peer dependency (#7268)
• babaf15 docs(migration): note that API 1.10.0 needs SDK 3.x (#7253)
• daae704 fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (...
• cc2a315 fix(otlp-grpc-exporter-base): avoid false mTLS configuration warnings (#7241)
• 29eec06 fix(sdk-node): warn and skip, instead of erroring, on an unknown resource det...
• 4667c0a docs: update dead semantic conventions resource specification links (#7254)
• Additional commits viewable in compare view

Updates @opentelemetry/resources from 3.0.0 to 3.1.0

Release notes

Sourced from @​opentelemetry/resources's releases.

v3.1.0

3.1.0

🚀 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(context-zone): declare the @opentelemetry/api peer dependency so Yarn PnP can resolve it for context-zone-peer-dep #7268 @​Vivek1898
• fix(core): accept attribute values with shared (non-circular) object references #7068 @​rajanpanth
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.
• fix(propagator-b3): reject trace ids that are not 16 or 32 characters long #7262 @​adityareddy-dev

📚 Documentation

• docs(resources): update dead semantic conventions resource specification links #7254 @​helmipradita
• docs(migration): note that @opentelemetry/api v1.10.0 needs SDK 3.x #7253 @​adityareddy-dev

🏠 Internal

• perf(sdk-logs, sdk-trace): wait for each distinct pending resource once per batch instead of once per record #7208 @​shehjaddev
• ci: update the W3C harness for Python 3.14 #7236 @​adityareddy-dev

Changelog

Sourced from @​opentelemetry/resources's changelog.

3.1.0

🚀 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(context-zone): declare the @opentelemetry/api peer dependency so Yarn PnP can resolve it for context-zone-peer-dep #7268 @​Vivek1898
• fix(core): accept attribute values with shared (non-circular) object references #7068 @​rajanpanth
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.
• fix(propagator-b3): reject trace ids that are not 16 or 32 characters long #7262 @​adityareddy-dev

📚 Documentation

• docs(resources): update dead semantic conventions resource specification links #7254 @​helmipradita
• docs(migration): note that @opentelemetry/api v1.10.0 needs SDK 3.x #7253 @​adityareddy-dev

🏠 Internal

• perf(sdk-logs, sdk-trace): wait for each distinct pending resource once per batch instead of once per record #7208 @​shehjaddev
• ci: update the W3C harness for Python 3.14 #7236 @​adityareddy-dev

Commits

• 9985264 chore: prepare next release (#7272)
• 7983f1c fix: raise @​opentelemetry/api peer floor to 1.10.0 where needed (

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml