build(deps): bump @opentelemetry/auto-instrumentations-node from 0.70.0 to 0.76.0 in /create-agents-template

[dependabot]

Bumps @opentelemetry/auto-instrumentations-node from 0.70.0 to 0.76.0.

Changelog

Sourced from @​opentelemetry/auto-instrumentations-node's changelog.

0.76.0 (2026-05-13)

Features

• deps: update deps matching '@opentelemetry/*' (#3523) (e26a90a)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​opentelemetry/instrumentation-amqplib bumped from ^0.64.0 to ^0.65.0
    • @​opentelemetry/instrumentation-aws-lambda bumped from ^0.69.0 to ^0.70.0
    • @​opentelemetry/instrumentation-aws-sdk bumped from ^0.72.0 to ^0.73.0
    • @​opentelemetry/instrumentation-bunyan bumped from ^0.62.0 to ^0.63.0
    • @​opentelemetry/instrumentation-cassandra-driver bumped from ^0.62.0 to ^0.63.0
    • @​opentelemetry/instrumentation-connect bumped from ^0.60.0 to ^0.61.0
    • @​opentelemetry/instrumentation-cucumber bumped from ^0.33.0 to ^0.34.0
    • @​opentelemetry/instrumentation-dataloader bumped from ^0.34.0 to ^0.35.0
    • @​opentelemetry/instrumentation-dns bumped from ^0.60.0 to ^0.61.0
    • @​opentelemetry/instrumentation-express bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-fs bumped from ^0.36.0 to ^0.37.0
    • @​opentelemetry/instrumentation-generic-pool bumped from ^0.60.0 to ^0.61.0
    • @​opentelemetry/instrumentation-graphql bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-hapi bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-ioredis bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-kafkajs bumped from ^0.26.0 to ^0.27.0
    • @​opentelemetry/instrumentation-knex bumped from ^0.61.0 to ^0.62.0
    • @​opentelemetry/instrumentation-koa bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-lru-memoizer bumped from ^0.61.0 to ^0.62.0
    • @​opentelemetry/instrumentation-memcached bumped from ^0.60.0 to ^0.61.0
    • @​opentelemetry/instrumentation-mongodb bumped from ^0.70.0 to ^0.71.0
    • @​opentelemetry/instrumentation-mongoose bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-mysql bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-mysql2 bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-nestjs-core bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-net bumped from ^0.61.0 to ^0.62.0
    • @​opentelemetry/instrumentation-openai bumped from ^0.15.0 to ^0.16.0
    • @​opentelemetry/instrumentation-oracledb bumped from ^0.42.0 to ^0.43.0
    • @​opentelemetry/instrumentation-pg bumped from ^0.69.0 to ^0.70.0
    • @​opentelemetry/instrumentation-pino bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-redis bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-restify bumped from ^0.62.0 to ^0.63.0
    • @​opentelemetry/instrumentation-router bumped from ^0.61.0 to ^0.62.0
    • @​opentelemetry/instrumentation-runtime-node bumped from ^0.30.0 to ^0.31.0
    • @​opentelemetry/instrumentation-socket.io bumped from ^0.64.0 to ^0.65.0
    • @​opentelemetry/instrumentation-tedious bumped from ^0.36.0 to ^0.37.0
    • @​opentelemetry/instrumentation-undici bumped from ^0.27.0 to ^0.28.0
    • @​opentelemetry/instrumentation-winston bumped from ^0.61.0 to ^0.62.0

... (truncated)

Commits

• See full diff 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8e7fec7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Thanks for the contribution! Your PR has been mirrored into Inkeep's internal monorepo, where review and merge happen. Your commit attribution is preserved as @dependabot[bot].

What happens next:

• An Inkeep maintainer will review the internal mirror PR.
• Reviewer comments are not automatically mirrored back to this thread. If you don't hear from us within a few business days, please comment here to nudge — that's the right thing to do.
• Once merged internally, the change will sync back to this repository and this PR will close automatically (don't be alarmed when it closes — that's how it lands).

For Inkeep maintainers (link goes to a private repo and is not accessible to external contributors): https://github.com/inkeep/agents-private/pull/935

See the repository's CONTRIBUTING.md for more context on how public PRs flow. This comment will be updated as the bridge state changes.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 7 days if no further activity occurs.

If this PR is still relevant:

• Rebase it on the latest main branch
• Add a comment explaining its current status
• Request a review if it's ready

Thank you for your contributions!