chore(deps): update module go.yaml.in/yaml/v2 to v3

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
go.yaml.in/yaml/v2	v2.4.4 → v3.0.5

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

yaml/go-yaml (go.yaml.in/yaml/v2)

v3.0.5

Compare Source

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • Between 02:00 AM and 04:59 AM, Monday through Friday (* 2-4 * * 1-5)
• 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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

Walkthrough

The indirect go.yaml.in/yaml/v3 dependency in go.mod is updated from v3.0.4 to v3.0.5; the go.yaml.in/yaml/v2 requirement remains unchanged.

Changes

YAML dependency update

Layer / File(s)	Summary
Update YAML module requirement go.mod	Updates the indirect go.yaml.in/yaml/v3 requirement to v3.0.5 while retaining go.yaml.in/yaml/v2 v2.4.4.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: smarthall, sam-nguyen7

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title states that go.yaml.in/yaml/v2 changes to v3, but the changeset updates go.yaml.in/yaml/v3 from v3.0.4 to v3.0.5.	Update the title to describe the actual patch-level bump of go.yaml.in/yaml/v3 from v3.0.4 to v3.0.5.

✅ Passed checks (14 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR only changes go.mod/go.sum; no Ginkgo test titles were added or modified, so the check is not applicable.
Test Structure And Quality	✅ Passed	PR only changes go.mod/go.sum; no test files or Ginkgo code were modified, so this review is not applicable.
Microshift Test Compatibility	✅ Passed	Only go.mod/go.sum changed; no new Ginkgo tests or MicroShift-incompatible APIs were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only go.mod and go.sum changed; no new Ginkgo e2e tests or cluster-topology assumptions were added.
Topology-Aware Scheduling Compatibility	✅ Passed	Only go.mod/go.sum changed for a YAML dependency bump; no manifests, controllers, or scheduling constraints were modified.
Ote Binary Stdout Contract	✅ Passed	Only go.mod/go.sum changed; no process-level stdout writes were added or modified, and main.go uses standard log (stderr by default).
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only go.mod/go.sum changed; no new Ginkgo e2e tests or networking assumptions were added.
No-Weak-Crypto	✅ Passed	Diff only bumps go.yaml.in/yaml/v3 in go.mod/go.sum; no MD5/SHA1/DES/RC4/3DES/Blowfish, ECB, or custom crypto code was added.
Container-Privileges	✅ Passed	PR only changes go.mod/go.sum; no container/K8s manifests or privilege settings were introduced.
No-Sensitive-Data-In-Logs	✅ Passed	PR only changes go.mod/go.sum to bump yaml deps; no code or logging changes, and no sensitive-data patterns appear in the diff.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/master/go.yaml.in-yaml-v2-3.x

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign abyrne55 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/lint	9b2e1d1	link	true	/test lint
ci/prow/scan	9b2e1d1	link	false	/test scan

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.