build(deps): update opentelemetry-js monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@opentelemetry/context-async-hooks (source)	1.17.0 -> 1.17.1
@opentelemetry/exporter-trace-otlp-http (source)	0.43.0 -> 0.44.0
@opentelemetry/instrumentation (source)	0.43.0 -> 0.44.0
@opentelemetry/instrumentation-http (source)	0.43.0 -> 0.44.0
@opentelemetry/resources (source)	1.17.0 -> 1.17.1
@opentelemetry/sdk-trace-base (source)	1.17.0 -> 1.17.1
@opentelemetry/sdk-trace-node (source)	1.17.0 -> 1.17.1
@opentelemetry/semantic-conventions (source)	1.17.0 -> 1.17.1

---

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/context-async-hooks)

v1.17.1

Compare Source

🐛 (Bug Fix)

• fix(sdk-trace-base): BatchSpanProcessor flushes when maxExportBatchSize is reached #​3958 @​nordfjord
• fix(sdk-metrics): allow instrument names to contain '/' #​4155
• fix(sdk-metrics): prevent per-reader storages from keeping unreported accumulations in memory #​4163 @​pichlermarc
  • fixes a memory leak which occurred when two or more MetricReader instances are registered to a MeterProvider
• fix(sdk-metrics): do not report empty scopes and metrics #​4135 @​pichlermarc
  • Instruments that were created, but did not have measurements will not be exported anymore
  • Meters (Scopes) that were created, but did not have any instruments with measurements under them will not be exported anymore.
• fix(exporter-zipkin): round duration to the nearest int in annotations to be compliant with zipkin protocol #​4167 @​FelipeEmerim

📚 (Refine Doc)

• docs(contributing): added guidelines for adding benchmark tests #​4169

🏠 (Internal)

• test: added a performance benchmark test for span creation #​4105
• test: added a workflow to run performance benchmark tests automatically #​4144

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate. View repository job log here.

[renovate-release]

🎉 This PR is included in version 37.34.2 🎉

The release is available on:

• GitHub release
• 37.34.2

Your semantic-release bot 📦🚀

[gizero]

@rarkins I haven't realised this was set to automerge. 🤦 We should have had something in place to prevent this (suggestions?). This PR rendered #25473 a useless effort...

[HonkingGoose]

@gizero do you want to try reverting to the known-good version of opentelemetry? I found a way to prevent Renovate automatically upgrading to the bad version. We could set dependencyDashboardApproval to true for just the opentelemetry packages that are breaking the OLTP export.

Here's a rough sketch of what you should put in our renovate.json file:

{
  "packageRules": [
    {
      "description": "Manually update opentelemetry when the opentelemetry export bug is fixed, see issue xxx",
      "matchPackagePatterns": ["^@package-name"],
      "dependencyDashboardApproval": true
    }
  ]
}

[gizero]

@HonkingGoose Thanks for the hint! Suggestion applied in #25503