Bump @opentelemetry/resources from 2.10.0 to 2.12.0

[dependabot]

Bumps @opentelemetry/resources from 2.10.0 to 2.12.0.

Release notes

Sourced from @​opentelemetry/resources's releases.

v2.12.0

2.12.0

🚀 Features

• chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #7086

🏠 Internal

• feat(ci): support releasing from maintenance branches #6767 @​pichlermarc
  • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.

v2.11.0

2.11.0

🚀 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

• fix(sdk-metrics): ignore Infinity in exponential histograms #7015 @​mwear

🏠 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

Changelog

Sourced from @​opentelemetry/resources's changelog.

2.12.0

🏠 Internal

• chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #7086
• feat(ci): support releasing from maintenance branches #6767 @​pichlermarc
  • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.

2.11.0

🚀 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

• fix(sdk-metrics): ignore Infinity in exponential histograms #7015 @​mwear

🏠 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

Commits

• 92b844e chore: prepare next v2.x release (#7151)
• a859aff fix(web-common): export getElementXPath utility (#7124)
• 2bd5a73 chore(web-common)!: deprecate addSpanNetworkEvents() et al instrumentation-...
• d60f05e doc(sdk-trace): add description for StackContextManager (#7089)
• 5bd476e chore: move context manager to sdk-trace (#7086)
• 554c0c6 chore: move sdk-trace-web utils to web-common (#7058)
• 788922c ci: support maintenance branch releases (#7036)
• 0b72a81 chore: prepare next release (#7044)
• a9c5338 ci: roll prerelease changelog into one final release changelog (#7045)
• f41805e chore: prepare next release (#7042)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, including the package name and old → new version, then check where that dependency is actually used in the codebase, or whether it is unused, and summarize the potential impact.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — Add a changelog entry only for changes that an Azurite user, operator, SDK developer, or extension user could reasonably observe. Exclude internal maintenance, testing, CI/CD, linting, and development dependency updates unless they result in a user-visible behaviour, compatibility, performance, or security improvement.
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — your final response must use the following structure exactly (no free-form paragraph summary).

Impact analysis

• Package:
• Old version:
• New version:
• Change Impact:

Build/Conflict Issues

• Commands:
• Result:

Tests

• Added:
• Updated:
• Result:

Run the Suite

• Commands:
• Status:

Changelog

• Entry:
• Location:

Comments

• Reviewed:
• Actions:

Self-Rate

• Score:
• Reasoning:

Summary

• Why this matters:
• Risk of not taking change:

[Copilot]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, i...

Impact analysis

• Package: @opentelemetry/resources
• Old version: 2.10.0
• New version: 2.12.0
• Change Impact: The direct production dependency is used by src/common/Telemetry.ts via resourceFromAttributes to create Azurite telemetry service identity attributes. package.json already allows 2.12.0 (^2.10.0); the PR updates the lockfile resolution. No application behavior change beyond using the newer telemetry resource implementation is expected.

Build/Conflict Issues

• Commands: npm ci --legacy-peer-deps, npm run build, npm run lint
• Result: All passed; no merge conflicts. npm reported five moderate advisories in the overall installed dependency tree; the GitHub advisory check found no vulnerability for @opentelemetry/resources@2.12.0.

Tests

• Added: None; no version-only test was added.
• Updated: None; existing meaningful coverage is in tests/common/Telemetry.test.ts.
• Result: All 11 telemetry tests passed, including assertions for Azurite resource attributes and emitted telemetry.

Run the Suite

• Commands: npm test
• Status: Passed: 947; pending: 4. The relevant GitHub Actions run remains in progress; 24 jobs had passed and no failed jobs were reported when checked.

Changelog

• Entry: None; this dependency maintenance update has no identified user-visible behavior change.
• Location: Not applicable.

Comments

• Reviewed: This request and PR review threads; the API returned no review threads.
• Actions: Completed the requested impact analysis and local install, build, lint, and test validation. No code changes were necessary.

Self-Rate

• Score: 10/10
• Reasoning: The requested local validations passed, relevant existing behavior is tested, no unnecessary changelog entry or version-only test was added, and the PR review threads were checked. GitHub Actions is still pending with no failures reported.

Summary

• Why this matters: Azurite's direct telemetry resource dependency now resolves to the requested 2.12.0 release.
• Risk of not taking change: The lockfile would continue resolving the direct dependency to 2.10.0 and miss intervening upstream improvements.