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

[renovate]

This PR contains the following updates:

Package	Update	Change
otel/opentelemetry-collector-contrib	minor	0.162.0 → 0.163.1

---

Release Notes

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

v0.163.1

Compare Source

---

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: semver-minor
Ecosystem: docker

Summary

Renovate bot proposes a minor Docker image bump of otel/opentelemetry-collector-contrib from 0.162.0 to 0.163.1, touching the otel source compose file and the generated stacks/observability.yml. The generated stack change is accompanied by a matching source change, so there is no source/generated drift. However, the release notes in the PR body for v0.163.1 are empty (only a compare link), so the changelog could not be checked and no breaking-change assessment can be made. Per policy, missing release-note context without a direct blocker yields a neutral decision.

Changed runtime artifacts

Image / dependency	From	To	Risk note
otel/opentelemetry-collector-contrib	0.162.0	0.163.1	minor bump for the OpenTelemetry Collector Contrib image; the linked release notes for v0.163.1 contain no changelog content in the PR context, so breaking-change impact cannot be verified

Runtime impact

Expected rolling update of the OpenTelemetry Collector containers across the observability stack; impact is unverified because release notes were unavailable.

Breaking change assessment

Unable to determine; the release notes for v0.163.1 provided in the PR context are empty and no changelog content was available to inspect.

Required checks

• ./stackctl.sh sync
• ./stackctl.sh up --dry-run --no-logs

Manual follow-up

• Review the upstream CHANGELOG for v0.163.1 to confirm no breaking config or processor/exporter changes affect the current otel collector configuration.
• Manually merge after validation since automerge is disabled by config.

Sources checked

• Dependabot metadata
• PR diff and changed file list
• PR body release notes (empty content)

[anitrend]

OpenCode risk gate: neutral. Manual review required. Risk: unknown. Reason: Renovate bot proposes a minor Docker image bump of otel/opentelemetry-collector-contrib from 0.162.0 to 0.163.1, touching the otel source compose file and the generated stacks/observability.yml. The generated stack change is accompanied by a matching source change, so there is no source/generated drift. However, the release notes in the PR body for v0.163.1 are empty (only a compare link), so the changelog could not be checked and no breaking-change assessment can be made. Per policy, missing release-note context without a direct blocker yields a neutral decision.

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