Data

Tools

Indexes

Applications

Experiments

Dependabot

An open index of dependabot pull requests across open source projects.

meta: bump the vercel group across 1 directory with 8 updates

Open
Number: #8201
Type: Pull Request
State: Open
Author: dependabot[bot] dependabot[bot]
Association: Contributor
Comments: 0
Created: October 02, 2025 at 10:44 PM UTC
(9 months ago)
Updated: October 02, 2025 at 10:44 PM UTC
(9 months ago)
Labels:
github_actions:pull-request
Description:

Bumps the vercel group with 8 updates in the / directory:

Package From To
turbo 2.5.6 2.5.8
@opentelemetry/api-logs 0.203.0 0.205.0
@opentelemetry/instrumentation 0.203.0 0.205.0
@opentelemetry/sdk-logs 0.203.0 0.205.0
@vercel/otel 1.13.0 2.0.0
next 15.5.2 15.5.4
next-intl 4.3.5 4.3.9
@next/eslint-plugin-next 15.5.2 15.5.4

Updates turbo from 2.5.6 to 2.5.8

Release notes

Sourced from turbo's releases.

Turborepo v2.5.8

What's Changed

create-turbo

Changelog

Full Changelog: https://github.com/vercel/turborepo/compare/v2.5.7...v2.5.8

Turborepo v2.5.8-canary.0

What's Changed

create-turbo

Changelog

Full Changelog: https://github.com/vercel/turborepo/compare/v2.5.7...v2.5.8-canary.0

Turborepo v2.5.7

What's Changed

Docs

create-turbo

eslint

@​turbo/repository

Examples

... (truncated)

Commits

Updates @opentelemetry/api-logs from 0.203.0 to 0.205.0

Release notes

Sourced from @​opentelemetry/api-logs's releases.

experimental/v0.205.0

0.205.0

:boom: Breaking Changes

  • fix(otlp-exporter-base)!: split node and browser config types in two #5917 @​pichlermarc
    • Fixes a bug where Node.js modules would be incorrectly used in the instantiation of a web-targeted exporter
    • Breaking changes:
      • (user-facing) createOtlpHttpExportDelegate(OtlpHttpConfiguration) has been changed to take a different, but identical type OtlpNodeHttpConfiguration to differentiate it from the web-targeted exporters
      • (user-facing) convertLegacyHttpOptions(...) now returns OtlpNodeHttpConfiguration, the returned object's contents remain identical.
      • (user-facing) agentFactory has been dropped from OtlpHttpConfiguration as it is node-specific and is now part of OtlpNodeHttpConfiguration instead

experimental/v0.204.0

0.204.0

:boom: Breaking Changes

  • feat(api-logs)!: Marked private methods as "conventionally private". #5789
  • feat(exporter-otlp-*): support custom HTTP agents #5719 @​raphael-theriault-swi
    • OtlpHttpConfiguration.agentOptions has been removed and functionality has been rolled into OtlpHttpConfiguration.agentFactory
      • (old) { agentOptions: myOptions }
      • (new) { agentFactory: httpAgentFactoryFromOptions(myOptions) }

:rocket: Features

  • feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
    • when using headers, the Browser exporter now prefers fetch over XMLHttpRequest if present. Sending via XMLHttpRequest will be removed in a future release.
  • feat(opentelemetry-configuration): creation of basic ConfigProvider #5809 @​maryliag
  • feat(opentelemetry-configuration): creation of basic FileConfigProvider #5863 @​maryliag
  • feat(sdk-node): Add support for multiple metric readers via the new metricReaders option in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The old metricReader (singular) option is now deprecated and will show a warning if used, but remains supported for backward compatibility. Comprehensive tests and documentation have been added. #5760

    • Migration:

      • Before:

        const sdk = new NodeSDK({ metricReader: myMetricReader });

      • After:

        const sdk = new NodeSDK({ metricReaders: [myMetricReader] });

    • Users should migrate to the new metricReaders array option for future compatibility. The old option will be removed in an upcoming experimental version.

  • feat(instrumentation-http): Added support for redacting specific url query string values and url credentials #5743 @​rads-1996

:bug: Bug Fixes

  • fix(otlp-exporter-base): prioritize esnext export condition as it is more specific #5458

... (truncated)

Commits

Updates @opentelemetry/instrumentation from 0.203.0 to 0.205.0

Release notes

Sourced from @​opentelemetry/instrumentation's releases.

experimental/v0.205.0

0.205.0

:boom: Breaking Changes

  • fix(otlp-exporter-base)!: split node and browser config types in two #5917 @​pichlermarc
    • Fixes a bug where Node.js modules would be incorrectly used in the instantiation of a web-targeted exporter
    • Breaking changes:
      • (user-facing) createOtlpHttpExportDelegate(OtlpHttpConfiguration) has been changed to take a different, but identical type OtlpNodeHttpConfiguration to differentiate it from the web-targeted exporters
      • (user-facing) convertLegacyHttpOptions(...) now returns OtlpNodeHttpConfiguration, the returned object's contents remain identical.
      • (user-facing) agentFactory has been dropped from OtlpHttpConfiguration as it is node-specific and is now part of OtlpNodeHttpConfiguration instead

experimental/v0.204.0

0.204.0

:boom: Breaking Changes

  • feat(api-logs)!: Marked private methods as "conventionally private". #5789
  • feat(exporter-otlp-*): support custom HTTP agents #5719 @​raphael-theriault-swi
    • OtlpHttpConfiguration.agentOptions has been removed and functionality has been rolled into OtlpHttpConfiguration.agentFactory
      • (old) { agentOptions: myOptions }
      • (new) { agentFactory: httpAgentFactoryFromOptions(myOptions) }

:rocket: Features

  • feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
    • when using headers, the Browser exporter now prefers fetch over XMLHttpRequest if present. Sending via XMLHttpRequest will be removed in a future release.
  • feat(opentelemetry-configuration): creation of basic ConfigProvider #5809 @​maryliag
  • feat(opentelemetry-configuration): creation of basic FileConfigProvider #5863 @​maryliag
  • feat(sdk-node): Add support for multiple metric readers via the new metricReaders option in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The old metricReader (singular) option is now deprecated and will show a warning if used, but remains supported for backward compatibility. Comprehensive tests and documentation have been added. #5760

    • Migration:

      • Before:

        const sdk = new NodeSDK({ metricReader: myMetricReader });

      • After:

        const sdk = new NodeSDK({ metricReaders: [myMetricReader] });

    • Users should migrate to the new metricReaders array option for future compatibility. The old option will be removed in an upcoming experimental version.

  • feat(instrumentation-http): Added support for redacting specific url query string values and url credentials #5743 @​rads-1996

:bug: Bug Fixes

  • fix(otlp-exporter-base): prioritize esnext export condition as it is more specific #5458

... (truncated)

Commits

Updates @opentelemetry/sdk-logs from 0.203.0 to 0.205.0

Release notes

Sourced from @​opentelemetry/sdk-logs's releases.

experimental/v0.205.0

0.205.0

:boom: Breaking Changes

  • fix(otlp-exporter-base)!: split node and browser config types in two #5917 @​pichlermarc
    • Fixes a bug where Node.js modules would be incorrectly used in the instantiation of a web-targeted exporter
    • Breaking changes:
      • (user-facing) createOtlpHttpExportDelegate(OtlpHttpConfiguration) has been changed to take a different, but identical type OtlpNodeHttpConfiguration to differentiate it from the web-targeted exporters
      • (user-facing) convertLegacyHttpOptions(...) now returns OtlpNodeHttpConfiguration, the returned object's contents remain identical.
      • (user-facing) agentFactory has been dropped from OtlpHttpConfiguration as it is node-specific and is now part of OtlpNodeHttpConfiguration instead

experimental/v0.204.0

0.204.0

:boom: Breaking Changes

  • feat(api-logs)!: Marked private methods as "conventionally private". #5789
  • feat(exporter-otlp-*): support custom HTTP agents #5719 @​raphael-theriault-swi
    • OtlpHttpConfiguration.agentOptions has been removed and functionality has been rolled into OtlpHttpConfiguration.agentFactory
      • (old) { agentOptions: myOptions }
      • (new) { agentFactory: httpAgentFactoryFromOptions(myOptions) }

:rocket: Features

  • feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
    • when using headers, the Browser exporter now prefers fetch over XMLHttpRequest if present. Sending via XMLHttpRequest will be removed in a future release.
  • feat(opentelemetry-configuration): creation of basic ConfigProvider #5809 @​maryliag
  • feat(opentelemetry-configuration): creation of basic FileConfigProvider #5863 @​maryliag
  • feat(sdk-node): Add support for multiple metric readers via the new metricReaders option in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The old metricReader (singular) option is now deprecated and will show a warning if used, but remains supported for backward compatibility. Comprehensive tests and documentation have been added. #5760

    • Migration:

      • Before:

        const sdk = new NodeSDK({ metricReader: myMetricReader });

      • After:

        const sdk = new NodeSDK({ metricReaders: [myMetricReader] });

    • Users should migrate to the new metricReaders array option for future compatibility. The old option will be removed in an upcoming experimental version.

  • feat(instrumentation-http): Added support for redacting specific url query string values and url credentials #5743 @​rads-1996

:bug: Bug Fixes

  • fix(otlp-exporter-base): prioritize esnext export condition as it is more specific #5458

... (truncated)

Commits

Updates @vercel/otel from 1.13.0 to 2.0.0

Release notes

Sourced from @​vercel/otel's releases.

@​vercel/otel@​2.0.0

Major Changes

  • #165 7887411 Thanks @​bengigone! - Add support for OTel JS SDK 2.X

    Breaking Changes

    1. OpenTelemetry SDK dependencies updated

    API package (minimum version bumped):

    • @opentelemetry/api: >=1.9.0 <3.0.0 (was >=1.7.0 <2.0.0)

    Stable packages (updated to v2.x):

    • @opentelemetry/resources: >=2.0.0 <3.0.0 (was >=1.19.0 <2.0.0)
    • @opentelemetry/sdk-metrics: >=2.0.0 <3.0.0 (was >=1.19.0 <2.0.0)
    • @opentelemetry/sdk-trace-base: >=2.0.0 <3.0.0 (was >=1.19.0 <2.0.0)

    Experimental packages (updated to v0.2XX):

    • @opentelemetry/api-logs: >=0.200.0 <0.300.0 (was >=0.46.0 <0.200.0)
    • @opentelemetry/instrumentation: >=0.200.0 <0.300.0 (was >=0.46.0 <0.200.0)
    • @opentelemetry/sdk-logs: >=0.200.0 <0.300.0 (was >=0.46.0 <0.200.0)

    2. Minimum Node.js version requirement

    The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0 to align with OpenTelemetry JS SDK 2.x requirements. This means that support for Node.js 14 and 16 has been dropped.

    3. Configuration changes

    Log Record Processors:

    // Before (v1.x)
registerOTel({
  serviceName: "your-service-name",
  logRecordProcessor: myProcessor, // Single processor
});

    // After (v2.x)
registerOTel({
serviceName: "your-service-name",
logRecordProcessors: [myProcessor], // Array of processors
});

    Metric Readers:

... (truncated)

Commits

Updates next from 15.5.2 to 15.5.4

Release notes

Sourced from next's releases.

v15.5.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix: ensure onRequestError is invoked when otel enabled (#83343)
  • fix: devtools initial position should be from next config (#83571)
  • [devtool] fix overlay styles are missing (#83721)
  • Turbopack: don't match dynamic pattern for node_modules packages (#83176)
  • Turbopack: don't treat metadata routes as RSC (#82911)
  • [turbopack] Improve handling of symlink resolution errors in track_glob and read_glob (#83357)
  • Turbopack: throw large static metadata error earlier (#82939)
  • fix: error overlay not closing when backdrop clicked (#83981)
  • Turbopack: flush Node.js worker IPC on error (#84077)

Misc Changes

  • [CNA] use linter preference (#83194)
  • CI: use KV for test timing data (#83745)
  • docs: september improvements and fixes (#83997)

Credits

Huge thanks to @​yiminghe, @​huozhi, @​devjiwonchoi, @​mischnic, @​lukesandberg, @​ztanner, @​icyJoseph, @​leerob, @​fufuShih, @​dwrth, @​aymericzip, @​obendev, @​molebox, @​OoMNoO, @​pontasan, @​styfle, @​HondaYt, @​ryuapp, @​lpalmes, and @​ijjk for helping!

v15.5.3

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix: validation return types of pages API routes (#83069)
  • fix: relative paths in dev in validator.ts (#83073)
  • fix: remove satisfies keyword from type validation to preserve old TS compatibility (#83071)

Credits

Huge thanks to @​bgub for helping!

Commits
  • 40f1d78 v15.5.4
  • cb30f0a [backport] docs: september improvements and fixes (#83997)
  • b6a32bb [backport] [CNA] use linter preference (#83194) (#84087)
  • 26d61f1 [backport] Turbopack: flush Node.js worker IPC on error (#84079)
  • e11e87a [backport] fix: error overlay not closing when backdrop clicked (#83981) (#83...
  • 0a29888 [backport] fix: devtools initial position should be from next config (#83571)...
  • 7a53950 [backport] Turbopack: don't treat metadata routes as RSC (#83804)
  • 050bdf1 [backport] Turbopack: throw large static metadata error earlier (#83816)
  • 1f6ea09 [backport] Turbopack: Improve handling of symlink resolution errors (#83805)
  • c7d1855 [backport] CI: use KV for test timing data (#83860)
  • Additional commits viewable in compare view

Updates next-intl from 4.3.5 to 4.3.9

Release notes

Sourced from next-intl's releases.

v4.3.9

4.3.9 (2025-09-15)

Bug Fixes

v4.3.8

4.3.8 (2025-09-12)

Bug Fixes

v4.3.7

4.3.7 (2025-09-09)

Bug Fixes

v4.3.6

4.3.6 (2025-09-04)

Bug Fixes

  • Ensure messages declaration continues working in next dev for upcoming next@15.5.1 (#2008) (2bf09ec) – by @​amannn
Changelog

Sourced from next-intl's changelog.

4.3.9 (2025-09-15)

Bug Fixes

4.3.8 (2025-09-12)

Bug Fixes

4.3.7 (2025-09-09)

Bug Fixes

4.3.6 (2025-09-04)

Bug Fixes

  • Ensure messages declaration continues working in next dev for upcoming next@15.5.1 (#2008) (2bf09ec) – by @​amannn
Commits
  • b927ead v4.3.9
  • c82d0af fix: Prefix pathnames when switching with useRouter to another locale (#2021)
  • 07149a1 docs: Fix link
  • 0c3c779 docs: Remove feedback link
  • d2c603d docs: Mention x-forwarded-host for alternate links
  • 42b440a docs: Fix outdated label
  • c9b065b v4.3.8
  • 31265b4 fix: Avoid double-encoding of already encoded params (#2017)
  • bc4e86e v4.3.7
  • bc9cb62 fix: Avoid usePathname inconsistency in Next.js leading to a hydration erro...
  • Additional commits viewable in compare view

Updates @next/eslint-plugin-next from 15.5.2 to 15.5.4

Release notes

Sourced from @​next/eslint-plugin-next's releases.

v15.5.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix: ensure onRequestError is invoked when otel enabled (#83343)
  • fix: devtools initial position should be from next config (#83571)
  • [devtool] fix overlay styles are missing (#83721)
  • Turbopack: don't match dynamic pattern for node_modules packages (#83176)
  • Turbopack: don't treat metadata routes as RSC (#82911)
  • [turbopack] Improve handling of symlink resolution errors in track_glob and read_glob (#83357)
  • Turbopack: throw large static metadata error earlier (#82939)
  • fix: error overlay not closing when backdrop clicked (#83981)
  • Turbopack: flush Node.js worker IPC on error (#84077)

Misc Changes

  • [CNA] use linter preference (#83194)
  • CI: use KV for test timing data (#83745)
  • docs: september improvements and fixes (#83997)

Credits

Huge thanks to @​yiminghe, @​huozhi, @​devjiwonchoi, @​mischnic, @​lukesandberg, @​ztanner, @​icyJoseph, @​leerob, @​fufuShih, @​dwrth, @​aymericzip, @​obendev, @​molebox, @​OoMNoO, @​pontasan, @​styfle, @​HondaYt, @​ryuapp, @​lpalmes, and @​ijjk for helping!

v15.5.3

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • fix: validation return types of pages API routes (#83069)
  • fix: relative paths in dev in validator.ts (#83073)
  • fix: remove satisfies keyword from type validation to preserve old TS compatibility (#83071)

Credits

Huge thanks to @​bgub for helping!

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
Pull Request Statistics
Commits:
1
Files Changed:
3
Additions:
+303
Deletions:
-270
Package Dependencies
Package:
next
Ecosystem:
npm
Version Change:
15.5.2 → 15.5.4
Update Type:
Patch
Package:
@vercel/otel
Ecosystem:
npm
Version Change:
1.13.0 → 2.0.0
Update Type:
Major
Package:
@next/eslint-plugin-next
Ecosystem:
npm
Version Change:
15.5.2 → 15.5.4
Update Type:
Patch
Package:
turbo
Ecosystem:
npm
Version Change:
2.5.6 → 2.5.8
Update Type:
Patch
Package:
@opentelemetry/instrumentation
Ecosystem:
npm
Version Change:
0.203.0 → 0.205.0
Update Type:
Minor
Package:
next-intl
Ecosystem:
npm
Version Change:
4.3.5 → 4.3.9
Update Type:
Patch
Package:
@opentelemetry/api-logs
Ecosystem:
npm
Version Change:
0.203.0 → 0.205.0
Update Type:
Minor
Package:
@opentelemetry/sdk-logs
Ecosystem:
npm
Version Change:
0.203.0 → 0.205.0
Update Type:
Minor
Actions
View on GitHub View Repository All Dependabot PRs
Technical Details
ID: 9246472
UUID: 2883278738
Node ID: PR_kwDOAj-F4s6r21eS
Host: GitHub
Repository: nodejs/nodejs.org
Merge State: Unknown