Skip to content

fix(deps): update opentelemetry-js monorepo - #136

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/opentelemetry-js-monorepo
Open

fix(deps): update opentelemetry-js monorepo#136
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/opentelemetry-js-monorepo

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@opentelemetry/core (source) 2.10.02.11.0 age confidence
@opentelemetry/exporter-trace-otlp-proto (source) ^0.221.0^0.222.0 age confidence
@opentelemetry/resources (source) 2.10.02.11.0 age confidence
@opentelemetry/sdk-trace-base (source) 2.10.02.11.0 age confidence

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/core)

v2.11.0

Compare Source

🚀 Features
  • feat(context-async-hooks): implement attach() on AsyncLocalStorageContextManager #​6845 @​pichlermarc
    • On Node.js 25.9+, delegates to AsyncLocalStorage.withScope() returning a native RunScope. On older Node.js, falls back to enterWith() with a manual disposable wrapper.
  • feat(sdk-trace): allow configuring the force flush timeout per call #​6929 @​LarryHu0217
🐛 Bug Fixes
🏠 Internal
  • perf(sdk-metrics): reuse a single DataView for exponential histogram bit reads #​6998 @​mwear
  • chore(ci): run documentation tests on a weekly schedule #​6920 @​LarryHu0217
  • feat(ci): support pre-releases and major version bumps in the release workflow #​6768 @​pichlermarc
  • chore(resources): Ensure that multiple uses of serviceInstanceIdDetector.detect() return the same value for service.instance.id

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate

renovate Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: clients/ts/pnpm-lock.yaml
Scope: all 5 workspace projects
✓ Lockfile passes supply-chain policies (verified 42s ago)
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 18, reused 0, downloaded 0, added 0
Progress: resolved 110, reused 0, downloaded 0, added 0
Progress: resolved 210, reused 0, downloaded 0, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 20 versions do not meet the minimumReleaseAge constraint:
  @opentelemetry/api-logs@0.222.0 was published at 2026-08-31T16:41:56.826Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/api-logs@0.222.0 was published at 2026-08-31T16:41:56.826Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/core@2.11.0 was published at 2026-08-31T16:40:56.131Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/core@2.11.0 was published at 2026-08-31T16:40:56.131Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/core@2.11.0 was published at 2026-08-31T16:40:56.131Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/core@2.11.0 was published at 2026-08-31T16:40:56.131Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/core@2.11.0 was published at 2026-08-31T16:40:56.131Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/core@2.11.0 was published at 2026-08-31T16:40:56.131Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/exporter-trace-otlp-proto@0.222.0 was published at 2026-08-31T16:42:51.690Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/otlp-exporter-base@0.222.0 was published at 2026-08-31T16:43:43.152Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/otlp-transformer@0.222.0 was published at 2026-08-31T16:44:10.006Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/otlp-transformer@0.222.0 was published at 2026-08-31T16:44:10.006Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/resources@2.11.0 was published at 2026-08-31T16:41:41.160Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/resources@2.11.0 was published at 2026-08-31T16:41:41.160Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/resources@2.11.0 was published at 2026-08-31T16:41:41.160Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/resources@2.11.0 was published at 2026-08-31T16:41:41.160Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/sdk-logs@0.222.0 was published at 2026-08-31T16:42:52.545Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/sdk-metrics@2.11.0 was published at 2026-08-31T16:41:30.260Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/sdk-trace@2.11.0 was published at 2026-08-31T16:43:58.168Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)
  @opentelemetry/sdk-trace@2.11.0 was published at 2026-08-31T16:43:58.168Z, within the minimumReleaseAge cutoff (2026-08-24T19:40:18.526Z)

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections August 31, 2026 19:40 Failure
@mergify

mergify Bot commented Aug 31, 2026

Copy link
Copy Markdown

Merge Protections

🔴 1 of 6 protections blocking · waiting on 🤖 CI

Protection Waiting on
🔴 🤖 Continuous Integration 🤖 CI
🟢 👀 Review Requirements
🟢 Enforce conventional commit
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queue

🔴 🤖 Continuous Integration

Waiting for

  • check-success=ci-gate
This rule is failing.
  • all of:
    • check-success=ci-gate

Show 5 satisfied protections

🟢 👀 Review Requirements

  • any of:
    • author = renovate[bot]
    • #approved-reviews-by>=2
    • author = dependabot[bot]
    • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants