Update dependency @vercel/otel to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vercel/otel	^1.13.0 -> ^2.1.0

---

Release Notes

vercel/otel (@​vercel/otel)

v2.1.0

Compare Source

Minor Changes

• #​181 14f773c Thanks @​dvoytenko! - Ignore auto-configuration based on the OTEL_EXPORTER_OTLP_ env vars when trace drains are used. This avoids duplicate trace export.

v2.0.1

Compare Source

Patch Changes

• #​170 9a695ad Thanks @​kakadiadarpan! - add project id to resource attributes

v2.0.0

Compare Source

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:**

```typescript
// 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:**

```typescript
// Before (v1.x)
registerOTel({
  serviceName: "your-service-name",
  metricReader: myReader, // Single reader
});

// After (v2.x)
registerOTel({
  serviceName: "your-service-name",
  metricReaders: [myReader], // Array of readers
});
```

Migration Guide

1.  **Update OpenTelemetry dependencies**: Update the OpenTelemetry packages you are using in your project to the compatible versions:

    **API package** (minimum version bumped):

    ```bash
    npm install @​opentelemetry/api@^1.9.0
    ```

    **Stable packages** (upgrade to v2.x):

    ```bash
    npm install @​opentelemetry/resources@^2.1.0 @​opentelemetry/sdk-trace-base@^2.1.0 @​opentelemetry/sdk-metrics@^2.1.0
    ```

    **Experimental packages** (upgrade to v0.2XX):

    ```bash
    npm install @​opentelemetry/sdk-logs@^0.205.0 @​opentelemetry/instrumentation@^0.205.0 @​opentelemetry/api-logs@^0.205.0
    ```

    **Note**: Only install the packages you are actually using in your project.

2.  **Update configuration**:

    **Log Record Processors** - Change `logRecordProcessor` to `logRecordProcessors`:

    ```typescript
    // Before
    registerOTel({
      serviceName: 'your-service-name',
      logRecordProcessor: myProcessor // Single processor
    });

    // After
    registerOTel({
      serviceName: 'your-service-name',
      logRecordProcessors: [myProcessor], // Array of processors
    });
    ```

    **Metric Readers** - Change `metricReader` to `metricReaders`:

    ```typescript
    // Before
    registerOTel({
      serviceName: 'your-service-name',
      metricReader: myReader, // Single processor
    });

    // After
    registerOtel({
      serviceName: 'your-service-name',
      metricReaders: [myReader], // Array of processors
    });
    ```

3.  **No code changes needed** for basic usage - the SDK interface remains the same for most common use cases.

For complete details on migrating from OpenTelemetry JS SDK 1.x to 2.x, see the [official OpenTelemetry migration guide](https://redirect.github.com/open-telemetry/opentelemetry-js/blob/v2.0.0/doc/upgrade-to-2.x.md).

v1.14.0

Compare Source

Minor Changes

• #​182 e44a0d8 Thanks @​dvoytenko! - Ignore auto-configuration based on the OTEL_EXPORTER_OTLP_ env vars when trace drains are used. This avoids duplicate trace export.

v1.13.1

Compare Source

Patch Changes

• #​171 2b353dd Thanks @​kakadiadarpan! - add project id to resource attributes

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
lobehub	Ready	Preview	Comment	Nov 2, 2025 1:32am
lobehub-lite	Building	Preview		Nov 2, 2025 1:32am

[gru-agent]

TestGru Assignment

Summary

Link	CommitId	Status	Reason
Detail	4cb7f76	🚫 Skipped	No files need to be tested {"packages/obervability-otel/package.json":"File path does not match include patterns."}

History Assignment

Tip

You can @gru-agent and leave your feedback. TestGru will make adjustments based on your input

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.62%. Comparing base (6b01095) to head (4cb7f76).
⚠️ Report is 6 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff            @@
##             next    #9969     +/-   ##
=========================================
  Coverage   83.62%   83.62%             
=========================================
  Files         950      950             
  Lines       65908    65908             
  Branches     9685     8017   -1668     
=========================================
  Hits        55113    55113             
  Misses      10795    10795             

Flag	Coverage Δ
app	78.77% <ø> (ø)
database	98.42% <ø> (ø)
packages/agent-runtime	98.37% <ø> (ø)
packages/context-engine	93.94% <ø> (ø)
packages/electron-server-ipc	93.76% <ø> (ø)
packages/file-loaders	92.21% <ø> (ø)
packages/model-bank	100.00% <ø> (ø)
packages/model-runtime	92.19% <ø> (ø)
packages/prompts	77.29% <ø> (ø)
packages/python-interpreter	96.50% <ø> (ø)
packages/utils	94.50% <ø> (ø)
packages/web-crawler	96.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Store	74.41% <ø> (ø)
Services	61.47% <ø> (ø)
Server	77.19% <ø> (ø)
Libs	35.68% <ø> (ø)
Utils	83.03% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lobehubbot]

👍 @renovate[bot]

Thank you for raising your pull request and contributing to our Community
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.
If you encounter any problems, please feel free to connect with us.