chore(all): update opentelemetry-go-contrib monorepo to v0.59.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.opentelemetry.io/contrib/exporters/autoexport	v0.53.0 -> v0.59.0
go.opentelemetry.io/contrib/propagators/autoprop	v0.53.0 -> v0.59.0

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (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 was generated by Mend Renovate. View the repository job log.

[forking-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: opentelemetry/instrumentation/app/go.sum

Command failed: install-tool golang 1.21.13

[code-review-assist]

Hi team,

I'm currently reviewing this pull request and will post my full review in a few minutes. In the meantime, here's a quick summary for you and other reviewers to get up to speed:

This pull request, submitted by Renovate, updates several OpenTelemetry Go contrib packages to their latest versions. The goal is to keep the golang-samples repository using the most up-to-date and secure versions of these libraries. This is a dependency update PR, and therefore no functional changes are expected.

Here's a breakdown of the changes:

• Updated Packages:

  • go.opentelemetry.io/contrib/detectors/gcp: Updated from v1.28.0 to v1.33.0
  • go.opentelemetry.io/contrib/exporters/autoexport: Updated from v0.53.0 to v0.58.0
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp: Updated from v0.53.0 to v0.58.0
  • go.opentelemetry.io/contrib/propagators/autoprop: Updated from v0.53.0 to v0.58.0

• Affected Files: The changes are reflected in the go.mod files within the opentelemetry/instrumentation/app and opentelemetry/trace directories. Specifically, the version numbers for the listed packages are updated within these files.

The full release notes for the updated opentelemetry-go-contrib monorepo are quite extensive and included in the PR description. I recommend reviewing them for a complete picture of all changes in the underlying libraries.

---

And now, a little haiku to lighten the mood:

Dependencies flow,
New versions, fresh and clean code,
Smooth sailing ahead.

Thanks,
Gemini

[code-review-assist]

This pull request updates several packages in the opentelemetry-go-contrib monorepo. It's good practice to keep dependencies up-to-date, and the provided table in the description is helpful for understanding the changes at a high level. The release notes are extensive and provide good context. However, consider summarizing the key changes and their potential impact on the project in the PR description itself. This will make it easier for reviewers to quickly assess the importance and risk of the update.

I've studied the release notes and the diff hunks and offer the following suggestions.

[code-review-assist]

Updating these opentelemetry-go-contrib packages is a good step. Could you elaborate in the PR description on why these specific versions were chosen? For example, are there any new features or bug fixes that are particularly relevant to this project? Referencing specific issues or sections of the release notes would be helpful. Additionally, it's important to consider the impact of dependency updates on the project's overall stability and performance. Are there any breaking changes introduced by these new versions? How do these updates affect the size and performance of the application?

[code-review-assist]

The update to go.opentelemetry.io/contrib/detectors/gcp from v1.28.0 to v1.33.0 is significant. The release notes mention several changes, including added support for SNS instrumentation and fixes for AWS presigned URLs and OTLP exporter configuration. It's important to ensure that these changes don't introduce any regressions in the project. Do you have any tests in place to verify the behavior of the GCP resource detector after this update? Specifically, it would be beneficial to add tests that cover the following scenarios:

• Verify that the resource detector correctly identifies the GCP environment.
• Ensure that the expected resource attributes are being collected.
• Confirm that no unexpected attributes are being added.
• Test any new functionality introduced in the updated version, such as SNS instrumentation support.

Consider adding these tests to the opentelemetry/trace/main_test.go file.

[forking-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.