chore(deps): update otel/opentelemetry-collector-contrib docker tag to v0.161.0

[renovate]

This PR contains the following updates:

Package	Update	Change
otel/opentelemetry-collector-contrib	minor	0.157.0 → 0.161.0

---

Release Notes

open-telemetry/opentelemetry-collector-releases (otel/opentelemetry-collector-contrib)

v0.161.0

Compare Source

🛑 Breaking changes 🛑

• all: Remove the deprecated mezmo exporter. (#​49953)
  Use the OTLP/HTTP exporter to send logs directly to Mezmo instead. See
  https://docs.mezmo.com/telemetry-pipelines/otel-collector and
  https://docs.mezmo.com/telemetry-pipelines/open-telemetry-source for migration guidance.

💡 Enhancements 💡

• otelcol-contrib: Upgrade go.opentelemetry.io/obi to v0.13.0 (#​1643)

v0.160.0

Compare Source

🚀 New components 🚀

• spanpruningprocessor: Added missing spanpruningprocessor to otelcol-contrib (#​1608)

💡 Enhancements 💡

• otelcol-contrib: Upgrade go.opentelemetry.io/obi to v0.11.0. (#​1604)

v0.159.0

Compare Source

🛑 Breaking changes 🛑

• contrib: Remove deprecated kafkatopicsobserver extension from the contrib distribution (#​1597)

🚀 New components 🚀

• extension/aws_iam_db_auth: Add aws_iam_db_auth to the contrib distribution (#​1591)

v0.158.0

Compare Source

🛑 Breaking changes 🛑

• all: Update Cosign usage to work with v3 (#​1570)
  The Cosign v3 upgrade introduced a change in signing workflow. Previous two files
  were required to map the outputs (certificate and signature), now only one file is required.
  The new file is a bundle that contains both outputs in JSON format.
  This change has been done following the guidance from https://goreleaser.com/blog/cosign-v3/.
  With this change, anyone who wants to verify the signature of the artifacts produced by the
  release will need to use Cosign V3 and point to the new bundle file or download the bundle and
  unpack it to get the certificate and signature files.

• all: Use split checksum for all binaries and distros (#​1582)
  The previous attempt at splitting the checksum file for AIX releases was not successful.
  The problem lies on the fac that .runtime.GOOS will always be the runtime of the compiled
  goreleaser binary ("linux" in this case). The only way to split the checksum file per target
  is what's implement here, but it ends up giving one checksum file per produced artifact.

🚀 New components 🚀

• icmpcheckreceiver: Add icmpcheckreceiver to the contrib distribution (#​1577)

💡 Enhancements 💡

• all: Add new binaries for aix/ppc64 (#​1424)

🧰 Bug fixes 🧰

• all: Skip Docker build and publish in AIX release job. (#​1580)
  The release for Contrib on AIX runs in its own job, where it doesn't build
  Docker images. The continue --merge phase of goreleaser runs all publishers
  by default, including the Docker manifests one. This will fail for AIX as
  the images aren't built.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[anitrend]

OpenCode Dependabot Risk Review

Schema: local-stack.dependabot-risk.v1

Decision: NEUTRAL
Risk: UNKNOWN
Automerge allowed: false
Update type: unknown
Ecosystem: unknown

Summary

OpenCode did not produce a valid risk classification. Manual review required. Reason: No valid JSON object in OpenCode output.

Changed runtime artifacts

No runtime image changes detected.

Runtime impact

Unknown.

Breaking change assessment

Not assessed because the OpenCode output was missing or invalid.

Required checks

Manual follow-up

• Review the dependency PR manually.
• Inspect the workflow logs for OpenCode output or parsing failure.

Sources checked

• PR diff
• PR metadata

[anitrend]

OpenCode risk gate: neutral. Manual review required. Risk: unknown. Reason: OpenCode did not produce a valid risk classification. Manual review required. Reason: No valid JSON object in OpenCode output.

[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.