fix(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace from 1.22.0 to 1.23.1 in /scheduler

[dependabot]

Bumps go.opentelemetry.io/otel/exporters/otlp/otlptrace from 1.22.0 to 1.23.1.

Release notes

Sourced from go.opentelemetry.io/otel/exporters/otlp/otlptrace's releases.

Release v1.23.0-rc.1

This is a release candidate for the v1.23.0 release. That release is expected to include the v1 release of the following modules:

• go.opentelemetry.io/otel/bridge/opencensus
• go.opentelemetry.io/otel/bridge/opencensus/test
• go.opentelemetry.io/otel/example/opencensus
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
• go.opentelemetry.io/otel/exporters/stdout/stdoutmetric

See our versioning policy for more information about these stability guarantees.

Changelog

Sourced from go.opentelemetry.io/otel/exporters/otlp/otlptrace's changelog.

[1.23.1] 2024-02-07

Fixed

• Register all callbacks passed during observable instrument creation instead of just the last one multiple times in go.opentelemetry.io/otel/sdk/metric. (#4888)

[1.23.0] 2024-02-06

This release contains the first stable, v1, release of the following modules:

• go.opentelemetry.io/otel/bridge/opencensus
• go.opentelemetry.io/otel/bridge/opencensus/test
• go.opentelemetry.io/otel/example/opencensus
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
• go.opentelemetry.io/otel/exporters/stdout/stdoutmetric

See our versioning policy for more information about these stability guarantees.

Added

• Add WithEndpointURL option to the exporters/otlp/otlpmetric/otlpmetricgrpc, exporters/otlp/otlpmetric/otlpmetrichttp, exporters/otlp/otlptrace/otlptracegrpc and exporters/otlp/otlptrace/otlptracehttp packages. (#4808)
• Experimental exemplar exporting is added to the metric SDK. See metric documentation for more information about this feature and how to enable it. (#4871)
• ErrSchemaURLConflict is added to go.opentelemetry.io/otel/sdk/resource. This error is returned when a merge of two Resources with different (non-empty) schema URL is attempted. (#4876)

Changed

• The Merge and New functions in go.opentelemetry.io/otel/sdk/resource now returns a partial result if there is a schema URL merge conflict. Instead of returning nil when two Resources with different (non-empty) schema URLs are merged the merged Resource, along with the new ErrSchemaURLConflict error, is returned. It is up to the user to decide if they want to use the returned Resource or not. It may have desired attributes overwritten or include stale semantic conventions. (#4876)

Fixed

• Fix ContainerID resource detection on systemd when cgroup path has a colon. (#4449)
• Fix go.opentelemetry.io/otel/sdk/metric to cache instruments to avoid leaking memory when the same instrument is created multiple times. (#4820)
• Fix missing Mix and Max values for go.opentelemetry.io/otel/exporters/stdout/stdoutmetric by introducing MarshalText and MarshalJSON for the Extrema type in go.opentelemetry.io/sdk/metric/metricdata. (#4827)

[1.23.0-rc.1] 2024-01-18

This is a release candidate for the v1.23.0 release. That release is expected to include the v1 release of the following modules:

• go.opentelemetry.io/otel/bridge/opencensus
• go.opentelemetry.io/otel/bridge/opencensus/test
• go.opentelemetry.io/otel/example/opencensus
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp

... (truncated)

Commits

• c5b112f Release v1.23.1/v0.43.2 (#4892)
• 11ebd19 Fix callback registration bug (#4888)
• e3eb3f7 Release v1.23.0/v0.45.1 (#4885)
• eabcef4 Return merged Resource on schema conflict (#4876)
• 2c7761d Bump benchmark-action/github-action-benchmark from 1.19.2 to 1.19.3 (#4883)
• f4e1e04 Bump lycheeverse/lychee-action from 1.9.2 to 1.9.3 (#4882)
• 569854e sdk/metric/metricdata: Add MarshalJSON for Extrema (#4827)
• 242d23a Remove the Flush method from Exemplar (#4873)
• fecb92e Add the experimental exemplar feature (#4871)
• d9d9507 stdouttrace: Refine example (#4872)
• 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)

[seldondev]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a SeldonIO or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.