chore: release main

[otelbot-js-contrib]

🤖 I have created a release beep boop

auto-instrumentations-node: 0.72.1

0.72.1 (2026-04-08)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @opentelemetry/instrumentation-express bumped from ^0.62.0 to ^0.62.1

auto-instrumentations-web: 0.59.1

0.59.1 (2026-04-08)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @opentelemetry/instrumentation-user-interaction bumped from ^0.58.0 to ^0.58.1

instrumentation-browser-navigation: 0.7.1

0.7.1 (2026-04-08)

Bug Fixes

• instr-browser-navigation: avoid unpatching history API (#3470) (f267476)

instrumentation-express: 0.62.1

0.62.1 (2026-04-08)

Bug Fixes

• instrumentation-express: end span on close event rather than finish (#3462) (fb1f127)

instrumentation-langchain: 0.3.0

0.3.0 (2026-04-08)

Features

• deps: update deps matching '@opentelemetry/*' (#3450) (c8df394)
• instrumentation-langchain: add initial package skeleton for instrumentation-langchain (#3132) (58285c4)

instrumentation-user-interaction: 0.58.1

0.58.1 (2026-04-08)

Bug Fixes

• instr-user-interaction: avoid wrapping/unwrapping browser APIs multiple times (#3459) (6d0205c)

---

This PR was generated with Release Please. See documentation.

[trentm]

@pichlermarc Do you think instr-langchain should NOT be in the release-please config files? I notice that this release-please PR was created immediately after the last one was merged (#3415), and only for instr-langchain.

Currently instr-langchain has private: true in its package.json. I think this is slightly confusing release-please. I don't know that it is causing harm though. The only side-effects are:

• instr-langchain is mentioned in chore: release main PRs, but is not actually released (GH release) or published (to npm)
• the instr-langchain version number in its package.json is artificually being bumped

/cc @hectorhdzg @yiyuan-he @mxiamxia (package maintainers)

[pichlermarc]

@trentm - it does not contain any code yet, so I think we should not have releases.

The current config does skip the release already:

opentelemetry-js-contrib/release-please-config.json

Lines 55 to 57 in c9d62be

	"packages/instrumentation-langchain": {
	"skip-github-release": true
	},

The previous release PR also listed it #3415 in the summary, but did not create a github release. So I think this is just release-please' way of dealing with that "skip-github-release": true. 🙂

As for changelog entries and versions that are not relased to npmjs.org: I think having these is fine; it's just "internal" versions for us to track the history. At some point there will be a feat(langchain): release initial version PR that will be at the top of the changelog then.