chore(deps): bump @opentelemetry/instrumentation from 0.203.0 to 0.204.0 in /packages/instrumentation-vertexai

[dependabot]

Bumps @opentelemetry/instrumentation from 0.203.0 to 0.204.0.

Release notes

Sourced from @​opentelemetry/instrumentation's releases.

experimental/v0.204.0

0.204.0

💥 Breaking Changes

• feat(api-logs)!: Marked private methods as "conventionally private". #5789
• feat(exporter-otlp-*): support custom HTTP agents #5719 @​raphael-theriault-swi
  • OtlpHttpConfiguration.agentOptions has been removed and functionality has been rolled into OtlpHttpConfiguration.agentFactory
    • (old) { agentOptions: myOptions }
    • (new) { agentFactory: httpAgentFactoryFromOptions(myOptions) }

🚀 Features

• feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
  • when using headers, the Browser exporter now prefers fetch over XMLHttpRequest if present. Sending via XMLHttpRequest will be removed in a future release.
• feat(opentelemetry-configuration): creation of basic ConfigProvider #5809 @​maryliag
• feat(opentelemetry-configuration): creation of basic FileConfigProvider #5863 @​maryliag
• feat(sdk-node): Add support for multiple metric readers via the new metricReaders option in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The old metricReader (singular) option is now deprecated and will show a warning if used, but remains supported for backward compatibility. Comprehensive tests and documentation have been added. #5760

  • Migration:

    • Before:

      const sdk = new NodeSDK({ metricReader: myMetricReader });

    • After:

      const sdk = new NodeSDK({ metricReaders: [myMetricReader] });

  • Users should migrate to the new metricReaders array option for future compatibility. The old option will be removed in an upcoming experimental version.

• feat(instrumentation-http): Added support for redacting specific url query string values and url credentials #5743 @​rads-1996

🐛 Bug Fixes

• fix(otlp-exporter-base): prioritize esnext export condition as it is more specific #5458
• fix(otlp-exporter-base): consider relative urls as valid in browser environments #5807
• fix(instrumentation-fetch): Use ESM version of semconv instead of CJS. Users expecting mixed ESM and CJS modules will now only get ESM modules. #5878 @​overbalance

🏠 Internal

• refactor(otlp-exporter-base): use getStringFromEnv instead of process.env #5594 @​weyert
• chore(sdk-logs): refactored imports #5801 @​svetlanabrennan
• refactor(instrumentation-grpc): updated path to semconv #5884 @​overbalance

Commits

• 98f9d72 chore: prepare next release (#5903)
• 4636de6 chore(deps): update dependency markdownlint-cli2 to v0.18.1 (#5891)
• ea83923 Add subscript to issue templates (#5831)
• daa4d39 chore(deps): lock file maintenance (#5904)
• af5c2fd chore: prepare next release (#5901)
• 747da91 feat(semantic-conventions): update semantic conventions to v1.37.0 (#5879)
• f2b0d2a chore(config): migrate renovate config (#5900)
• 52ffa04 chore: group packages that need to be updated together (#5896)
• 16c786c chore(deps): lock file maintenance (#5781)
• a171a5c chore(deps): update dependency mocha to v11.7.2 (#5850)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

---

Important

Bump @opentelemetry/instrumentation from 0.203.0 to 0.204.0 in package.json.

• Dependencies:
  • Bump @opentelemetry/instrumentation from 0.203.0 to 0.204.0 in package.json.

^{This description was created by for 10afa51. You can customize this summary. It will automatically update as commits are pushed.}

[dependabot]

Labels

The following labels could not be found: instrumentation-vertexai. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 10afa51 in 29 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. packages/instrumentation-vertexai/package.json:42

• Draft comment:
  Bump @opentelemetry/instrumentation from ^0.203.0 to ^0.204.0. Please verify that the breaking changes (e.g., private methods marked as conventionally private) do not impact our usage in VertexAI instrumentation. Ensure tests are run post-update.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is related to a dependency update, specifically bumping a version of a library. It asks the PR author to verify breaking changes and ensure tests are run, which violates the rules against asking for confirmation or testing. The comment does not provide a specific code suggestion or point out a specific issue with the code.

Workflow ID: wflow_QT6MjRFICVqx1Mbb

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}