feat(deps): Bump @opentelemetry/resources from 1.25.1 to 1.26.0

[dependabot]

Bumps @opentelemetry/resources from 1.25.1 to 1.26.0.

Release notes

Sourced from @​opentelemetry/resources's releases.

semconv/v1.26.0

@opentelemetry/[email protected]

Note: This package will now be versioned according to the version of semantic conventions being provided.

🚀 (Enhancement)

• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.

v1.26.0

1.26.0

🚀 (Enhancement)

• feat: include instrumentation scope info in console span and log record exporters #4848 @​blumamir
• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
  • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

🐛 (Bug Fix)

• fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @​trentm
• deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @​lforst
• fix(instrumentation): Fix optional property types #4833 @​alecmev
• fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @​danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @​robbkidd
  • Packages updated:
    • opentelemetry-context-zone
    • opentelemetry-core
    • opentelemetry-exporter-jaeger
    • opentelemetry-exporter-zipkin
    • opentelemetry-propagator-b3
    • opentelemetry-propagator-jaeger
    • opentelemetry-sdk-trace-base
    • opentelemetry-sdk-trace-node
    • opentelemetry-sdk-trace-web
    • propagator-aws-xray
    • sdk-metrics
• deps(sdk-metrics): remove unused lodash.merge dependency #4905 @​pichlermarc

Changelog

Sourced from @​opentelemetry/resources's changelog.

1.26.0

🚀 (Enhancement)

• feat: include instrumentation scope info in console span and log record exporters #4848 @​blumamir
• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
  • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

🐛 (Bug Fix)

• fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @​trentm
• deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @​lforst
• fix(instrumentation): Fix optional property types #4833 @​alecmev
• fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @​danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @​robbkidd
  • Packages updated:
    • opentelemetry-context-zone
    • opentelemetry-core
    • opentelemetry-exporter-jaeger
    • opentelemetry-exporter-zipkin
    • opentelemetry-propagator-b3
    • opentelemetry-propagator-jaeger
    • opentelemetry-sdk-trace-base
    • opentelemetry-sdk-trace-node
    • opentelemetry-sdk-trace-web
    • propagator-aws-xray
    • sdk-metrics
• deps(sdk-metrics): remove unused lodash.merge dependency #4905 @​pichlermarc

Commits

• 720bc8c chore: prepare next release (#4960)
• 65cedf7 chore: prepare next release (#4949)
• bd25230 docs: document console exporter output stability (#4956)
• 948496d chore: pin unit test to node 22.6 until 22.8 is available (#4957)
• 966ac17 docs: Describe support for ESM (#4876)
• 2ca2459 test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...
• c398601 feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)
• 3cf1c52 chore: prepare next release (#4939)
• 5578a11 chore: sync package-lock.json (#4947)
• 5c1ae0a docs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...
• 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 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 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)

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[AbhiPrasad]

Closing in favour of a more central PR: #13627

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.