Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 1, 2025

Bumps the vercel group with 7 updates:

Package From To
turbo 2.5.2 2.5.4
@opentelemetry/api-logs 0.200.0 0.201.1
@opentelemetry/instrumentation 0.200.0 0.201.1
@opentelemetry/sdk-logs 0.200.0 0.201.1
@vercel/otel 1.11.0 1.12.0
next 15.3.1 15.3.3
@next/eslint-plugin-next 15.3.1 15.3.3

Updates turbo from 2.5.2 to 2.5.4

Release notes

Sourced from turbo's releases.

Turborepo v2.5.4

What's Changed

Docs

turbo-ignore

eslint

@​turbo/repository

Examples

Changelog

... (truncated)

Commits

Updates @opentelemetry/api-logs from 0.200.0 to 0.201.1

Release notes

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

experimental/v0.201.1

0.201.1

🐛 Bug Fixes

  • fix(instrumentation): Change SemconvStability export from const enum to enum to allow single-file transpilation tooling to work with code that uses SemconvStability. #5691 @​trentm

experimental/v0.201.0

0.201.0

🚀 Features

  • feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
    • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
  • feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
    • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
  • feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
  • feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

🏠 Internal

  • refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
  • refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
    • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
  • refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
  • chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
  • chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
  • test: test Node.js 24 in CI #5661 @​cjihrig
Commits
  • 9dbd1e4 chore: prepare next release (#5696)
  • 4e2703c fix(instrumentation): change SemconvStability export from const enum to `...
  • 072d8a8 refactor(semantic-conventions): use weaver 'file_name' template config (#5689)
  • 04545fa refactor(semantic-conventions): tweak the leading spacing of comments on enum...
  • baec0a3 refactor(semantic-conventions): weaver 0.13.0 supports a 'stable_only' arg to...
  • 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
  • 6803723 fix(deps): update all patch versions (#5685)
  • d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
  • 56610a0 test: test Node.js 24 in CI (#5661)
  • 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
  • Additional commits viewable in compare view

Updates @opentelemetry/instrumentation from 0.200.0 to 0.201.1

Release notes

Sourced from @​opentelemetry/instrumentation's releases.

experimental/v0.201.1

0.201.1

🐛 Bug Fixes

  • fix(instrumentation): Change SemconvStability export from const enum to enum to allow single-file transpilation tooling to work with code that uses SemconvStability. #5691 @​trentm

experimental/v0.201.0

0.201.0

🚀 Features

  • feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
    • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
  • feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
    • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
  • feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
  • feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

🏠 Internal

  • refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
  • refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
    • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
  • refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
  • chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
  • chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
  • test: test Node.js 24 in CI #5661 @​cjihrig
Commits
  • 9dbd1e4 chore: prepare next release (#5696)
  • 4e2703c fix(instrumentation): change SemconvStability export from const enum to `...
  • 072d8a8 refactor(semantic-conventions): use weaver 'file_name' template config (#5689)
  • 04545fa refactor(semantic-conventions): tweak the leading spacing of comments on enum...
  • baec0a3 refactor(semantic-conventions): weaver 0.13.0 supports a 'stable_only' arg to...
  • 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
  • 6803723 fix(deps): update all patch versions (#5685)
  • d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
  • 56610a0 test: test Node.js 24 in CI (#5661)
  • 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
  • Additional commits viewable in compare view

Updates @opentelemetry/sdk-logs from 0.200.0 to 0.201.1

Release notes

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

experimental/v0.201.1

0.201.1

🐛 Bug Fixes

  • fix(instrumentation): Change SemconvStability export from const enum to enum to allow single-file transpilation tooling to work with code that uses SemconvStability. #5691 @​trentm

experimental/v0.201.0

0.201.0

🚀 Features

  • feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
    • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
  • feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
    • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
  • feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
  • feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

🏠 Internal

  • refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
  • refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
    • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
  • refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
  • chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
  • chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
  • test: test Node.js 24 in CI #5661 @​cjihrig
Commits
  • 9dbd1e4 chore: prepare next release (#5696)
  • 4e2703c fix(instrumentation): change SemconvStability export from const enum to `...
  • 072d8a8 refactor(semantic-conventions): use weaver 'file_name' template config (#5689)
  • 04545fa refactor(semantic-conventions): tweak the leading spacing of comments on enum...
  • baec0a3 refactor(semantic-conventions): weaver 0.13.0 supports a 'stable_only' arg to...
  • 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
  • 6803723 fix(deps): update all patch versions (#5685)
  • d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
  • 56610a0 test: test Node.js 24 in CI (#5661)
  • 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
  • Additional commits viewable in compare view

Updates @vercel/otel from 1.11.0 to 1.12.0

Release notes

Sourced from @​vercel/otel's releases.

@​vercel/otel@​1.12.0

Minor Changes

  • 26167e7: Fixes an issue where VERCEL_OTEL_ENDPOINTS is not set
Commits

Updates next from 15.3.1 to 15.3.3

Release notes

Sourced from next's releases.

v15.3.3

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

Core Changes

  • Reinstate vary (#79939)
  • fix(next-swc): Fix interestingness detection for React Compiler (#79558)
  • fix(next-swc): Fix react compiler usefulness detector (#79480)
  • fix(dev-overlay): Better handle edge-case file paths in launchEditor (#79526)
  • Client router should discard stale prefetch entries for static pages (#79362)

Credits

Huge thanks to @​gaojude, @​kdy1, @​bgw, and @​unstubbable for helping!

v15.3.2

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

Core Changes

  • backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOutput (#78488) (#78883)
  • @​next/mdx: Use stable turbopack config options (#78880)
  • Fix react-compiler: Fix detection of interest (#78879)
  • Fix turbopack: Backport sourcemap bugfix (#78881)
  • [next-server] preserve rsc query for rsc redirects (#78876)
  • Update middleware public/static matching (#78875)

Credits

Huge thanks to @​ijjk, @​huozhi, @​kdy1, @​wbinnssmith, and @​bgw for helping!

Commits
  • 3ab8db7 v15.3.3
  • 18c8113 [backport] Reinstate vary (#79939)
  • e18212f re-enable vary header deploy test (#79753)
  • ec202ec Revert "[next-server] skip setting vary header for basic routes" (#79426)
  • e2f264f fix(next-swc): Fix interestingness detection for React Compiler (15.3) (#79558)
  • 562fac7 fix(next-swc): Fix react compiler usefulness detector (15.3) (#79480)
  • 06097fd fix(dev-overlay): Better handle edge-case file paths in launchEditor (#79526)
  • bda731f Client router should discard stale prefetch entries for static pages (#79362)
  • d9ec4a4 v15.3.2
  • 3def5ff backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOu...
  • Additional commits viewable in compare view

Updates @next/eslint-plugin-next from 15.3.1 to 15.3.3

Release notes

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

v15.3.3

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

Core Changes

  • Reinstate vary (#79939)
  • fix(next-swc): Fix interestingness detection for React Compiler (#79558)
  • fix(next-swc): Fix react compiler usefulness detector (#79480)
  • fix(dev-overlay): Better handle edge-case file paths in launchEditor (#79526)
  • Client router should discard stale prefetch entries for static pages (#79362)

Credits

Huge thanks to @​gaojude, @​kdy1, @​bgw, and @​unstubbable for helping!

v15.3.2

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

Core Changes

  • backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOutput (#78488) (#78883)
  • @​next/mdx: Use stable turbopack config options (#78880)
  • Fix react-compiler: Fix detection of interest (#78879)
  • Fix turbopack: Backport sourcemap bugfix (#78881)
  • [next-server] preserve rsc query for rsc redirects (#78876)
  • Update middleware public/static matching (#78875)

Credits

Huge thanks to @​ijjk, @​huozhi, @​kdy1, @​wbinnssmith, and @​bgw 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

@dependabot dependabot bot added the github_actions:pull-request Trigger Pull Request Checks label Jun 1, 2025
@dependabot dependabot bot requested a review from a team as a code owner June 1, 2025 17:51
@dependabot dependabot bot added the github_actions:pull-request Trigger Pull Request Checks label Jun 1, 2025
@vercel
Copy link

vercel bot commented Jun 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
nodejs-org ⬜️ Ignored (Inspect) Visit Preview Jun 3, 2025 10:58am

@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jun 1, 2025
@codecov
Copy link

codecov bot commented Jun 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.46%. Comparing base (1d5a7f2) to head (d77311b).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7819      +/-   ##
==========================================
- Coverage   75.47%   75.46%   -0.02%     
==========================================
  Files         101      101              
  Lines        8309     8309              
  Branches      218      218              
==========================================
- Hits         6271     6270       -1     
- Misses       2036     2037       +1     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@MattIPv4
Copy link
Member

MattIPv4 commented Jun 1, 2025

@dependabot recreate

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vercel-5f27244db1 branch from 54a6bbb to 0e9468a Compare June 1, 2025 20:22
@MattIPv4 MattIPv4 added the github_actions:pull-request Trigger Pull Request Checks label Jun 1, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jun 1, 2025
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vercel-5f27244db1 branch 3 times, most recently from 6f57e90 to 8ec2687 Compare June 3, 2025 10:27
Bumps the vercel group with 7 updates:

| Package | From | To |
| --- | --- | --- |
| [turbo](https://github.com/vercel/turborepo) | `2.5.2` | `2.5.4` |
| [@opentelemetry/api-logs](https://github.com/open-telemetry/opentelemetry-js) | `0.200.0` | `0.201.1` |
| [@opentelemetry/instrumentation](https://github.com/open-telemetry/opentelemetry-js) | `0.200.0` | `0.201.1` |
| [@opentelemetry/sdk-logs](https://github.com/open-telemetry/opentelemetry-js) | `0.200.0` | `0.201.1` |
| [@vercel/otel](https://github.com/vercel/otel) | `1.11.0` | `1.12.0` |
| [next](https://github.com/vercel/next.js) | `15.3.1` | `15.3.3` |
| [@next/eslint-plugin-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-plugin-next) | `15.3.1` | `15.3.3` |


Updates `turbo` from 2.5.2 to 2.5.4
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/release.md)
- [Commits](vercel/turborepo@v2.5.2...v2.5.4)

Updates `@opentelemetry/api-logs` from 0.200.0 to 0.201.1
- [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.200.0...experimental/v0.201.1)

Updates `@opentelemetry/instrumentation` from 0.200.0 to 0.201.1
- [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.200.0...experimental/v0.201.1)

Updates `@opentelemetry/sdk-logs` from 0.200.0 to 0.201.1
- [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.200.0...experimental/v0.201.1)

Updates `@vercel/otel` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/vercel/otel/releases)
- [Commits](https://github.com/vercel/otel/compare/@vercel/otel@1.11.0...@vercel/otel@1.12.0)

Updates `next` from 15.3.1 to 15.3.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.3.1...v15.3.3)

Updates `@next/eslint-plugin-next` from 15.3.1 to 15.3.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v15.3.3/packages/eslint-plugin-next)

---
updated-dependencies:
- dependency-name: turbo
  dependency-version: 2.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: vercel
- dependency-name: "@opentelemetry/api-logs"
  dependency-version: 0.201.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: vercel
- dependency-name: "@opentelemetry/instrumentation"
  dependency-version: 0.201.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: vercel
- dependency-name: "@opentelemetry/sdk-logs"
  dependency-version: 0.201.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: vercel
- dependency-name: "@vercel/otel"
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: vercel
- dependency-name: next
  dependency-version: 15.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: vercel
- dependency-name: "@next/eslint-plugin-next"
  dependency-version: 15.3.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: vercel
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vercel-5f27244db1 branch from 8ec2687 to d77311b Compare June 3, 2025 10:58
@avivkeller avivkeller added the github_actions:pull-request Trigger Pull Request Checks label Jun 3, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jun 3, 2025
@avivkeller avivkeller added this pull request to the merge queue Jun 3, 2025
Merged via the queue into main with commit e29253b Jun 3, 2025
15 checks passed
@avivkeller avivkeller deleted the dependabot/npm_and_yarn/vercel-5f27244db1 branch June 3, 2025 11:25
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.

3 participants