chore(deps): update github.com/dprotaso/go-yit digest to 6f1ed93

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
github.com/dprotaso/go-yit	indirect	digest	9ba8df1 → 6f1ed93

---

Warning

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

---

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

This PR refines the Go module configuration by pinning the toolchain, replacing a deprecated runtime dependency with a yaml processor, bumping the go-yit indirect digest, and updating core Go modules.

File-Level Changes

Change	Details	Files
Normalize Go version directive and pin toolchain	Bump go directive from 1.23 to 1.23.0 Add toolchain specification go1.23.9	go.mod
Replace deprecated oapi-codegen/runtime with oasdiff/yaml	Remove oapi-codegen/runtime dependency Add oasdiff/yaml dependency Eliminate duplicate yaml entry	go.mod
Update github.com/dprotaso/go-yit indirect dependency digest	Bump go-yit version to v0.0.0-20250513224043-18a80f8f6df4	go.mod
Upgrade ancillary Go modules	Bump golang.org/x/sys to v0.31.0 Bump golang.org/x/text to v0.23.0	go.mod

---

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.

[Hyperkid123]

/retest

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@go.mod`:
- Around line 60-61: Replace legacy gopkg.in YAML module entries with the
official go.yaml.in paths: remove references to gopkg.in/yaml.v2 and
gopkg.in/yaml.v3 and ensure go.mod uses go.yaml.in/yaml/v2 (e.g., v2.4.3) and
go.yaml.in/yaml/v3 or v4 as appropriate (e.g., go.yaml.in/yaml/v4 v4.0.0-rc.4)
so there aren’t mixed import paths; update any import statements or indirect
requirements that still reference gopkg.in to point to go.yaml.in/yaml/* and
then run go get ./... and go mod tidy to reconcile versions and regenerate the
go.sum.