chore: prepare next release

[opentelemetrybot]

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

0.53.0

💥 Breaking Change

• fix(instrumentation)!:remove unused description property from interface #4847 @blumamir
• feat(exporter--otlp-)!: use transport interface in node.js exporters #4743 @pichlermarc
  • (user-facing) headers was intended for internal use has been removed from all exporters
  • (user-facing) compression was intended for internal use and has been removed from all exporters
  • (user-facing) hostname was intended for use in tests and is not used by any exporters, it will be removed in a future release
• fix(exporter--otlp-)!: ensure User-Agent header cannot be overwritten by the user #4743 @pichlermarc
  • allowing overrides of the User-Agent header was not specification compliant.
• feat(exporter--otlp)!: remove environment-variable specific code from browser exporters
  • (user-facing) removes the ability to configure browser exporters by using process.env polyfills
• feat(sdk-node)!: Automatically configure logs exporter #4740
• feat(exporter--otlp-)!: use transport interface in browser exporters #4895 @pichlermarc
  • (user-facing) protected headers property was intended for internal use has been removed from all exporters

🚀 (Enhancement)

• feat(otlp-transformer): Do not limit @opentelemetry/api upper range peerDependency #4816 @mydea
• feat(instrumentation-http): Allow to opt-out of instrumenting incoming/outgoing requests #4643 @mydea
• feat(sampler-jaeger-remote): added support of jaeger-remote-sampler according to this spec #4534 @legalimpurity

🐛 (Bug Fix)

• fix(instrumentation): ensure .setConfig() results in config.enabled defaulting to true #4941 @trentm
• fix(instrumentation-http): Ensure instrumentation of http.get and https.get work when used in ESM code #4857 @trentm
• fix(api-logs): align AnyValue to spec #4893 @blumamir
• fix(instrumentation): remove diag.debug() message for instrumentations that do not patch modules #4925 @trentm

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @robbkidd
  • Packages updated:
    • api-events
    • api-logs
    • opentelemetry-browser-detector
    • opentelemetry-exporter-prometheus
    • opentelemetry-instrumentation-fetch
    • opentelemetry-instrumentation-http
    • opentelemetry-instrumentation-xml-http-request
    • opentelemetry-instrumentation

[trentm]

This is an "interesting" change. Was this intentional?

Ah, I see. The @opentelemetry/core dep here was added after the previous release: https://github.com/open-telemetry/opentelemetry-js/pull/4880/files#diff-e4887234120ee9d59d36d48dbc50fcfc91d62eb3ad969aa43838da1f28b706a4

So, yes, I think this update is fine.