fix(deps): update otel core experimental to ^0.34.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@opentelemetry/instrumentation (source)	^0.32.0 -> ^0.34.0
@opentelemetry/instrumentation-http (source)	0.30.0 -> 0.34.0

---

Release Notes

open-telemetry/opentelemetry-js

v0.34.0

Compare Source

v0.33.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 3am on Friday" (UTC), 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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[vmarchaud]

not needed after #1278

[SimenB]

(plus #1289 and #1285)

[AnishLushte07]

Which version of @opentelemetry/auto-instrumentations-node has @opentelemetry/[email protected] ?.
I'm currently using @opentelemetry/[email protected] which still uses @opentelemetry/[email protected] , causing package dependency issue. Can you please help. Thanks is advance

[SimenB]

#1269 (comment)

[Flarna]

Does anyone know if closing this causes that renovate will no longer create PRs to update core/experimental?

1.9.0/0.35.0 has been released a few days ago but still no PR here....

[legendecas]

We previously closed node.js v17 update open-telemetry/opentelemetry-js#3203 and it can still propose a v19 update open-telemetry/opentelemetry-js#3350.

As 1.9.0/0.35.0 just got released last week, I assume lags may exist in renovate's bot. Renovate only runs on Friday: https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/renovate.json#L31. We can wait for another Friday for it to catch up.

[SimenB]

@legendecas people with edit capabilities should be able to tick the box under "Awaiting Schedule" in the dashboard issue: #637

[legendecas]

@SimenB thanks, clicked!

[SimenB]

#1357 showed up 👍