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

[red-hat-konflux]

This PR contains the following updates:

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

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

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

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: (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

---

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.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update YAML dependency usage to prefer go.yaml.in/yaml/v3 v3.0.4 and adjust go.yaml.in/yaml/v2 entry accordingly in module metadata.

File-Level Changes

Change	Details	Files
Adjust module dependencies to use YAML v3 and align v2 module entry in go.mod/go.sum.	Modify go.mod to add/ensure go.yaml.in/yaml/v3 v3.0.4 as an indirect dependency. Update the existing go.yaml.in/yaml/v2 indirect dependency version reference to keep module metadata consistent with tooling expectations. Regenerate go.sum entries to reflect the updated YAML module versions and checksums.	go.mod go.sum

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The go.mod change appears to downgrade go.yaml.in/yaml/v2 from v2.4.4 to v2.4.3 while also adding v3.0.4; double‑check whether v2 is still required and either remove it or align the version with the intended upgrade.
• If the project is meant to adopt yaml v3, ensure any import paths in the codebase are updated from go.yaml.in/yaml/v2 to go.yaml.in/yaml/v3 so the new dependency is actually used.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The go.mod change appears to downgrade go.yaml.in/yaml/v2 from v2.4.4 to v2.4.3 while also adding v3.0.4; double‑check whether v2 is still required and either remove it or align the version with the intended upgrade.
- If the project is meant to adopt yaml v3, ensure any import paths in the codebase are updated from go.yaml.in/yaml/v2 to go.yaml.in/yaml/v3 so the new dependency is actually used.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}