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

[red-hat-konflux]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum

Command failed: go get -t ./...
go: downloading github.com/mattn/go-sqlite3 v1.14.42
go: downloading github.com/jackc/pgx/v5 v5.9.1
go: downloading github.com/go-sql-driver/mysql v1.9.3
go: downloading go.yaml.in/yaml/v2 v2.4.3
go: github.com/RedHatInsights/quickstarts imports
	github.com/RedHatInsights/quickstarts/pkg/generated: cannot find module providing package github.com/RedHatInsights/quickstarts/pkg/generated

File name: go.mod

Post-upgrade command 'make generate' has not been added to the allowed list in allowedCommands

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: e9df16fb-d5ad-4645-a757-3852a0ee3bd5

📥 Commits

Reviewing files that changed from the base of the PR and between e1ab475 and 80e6e13.

📒 Files selected for processing (1)

• go.mod

✅ Files skipped from review due to trivial changes (1)

• go.mod

---

Summary by CodeRabbit

• Chores
  • Updated an internal YAML-related dependency to a newer major version to improve stability and compatibility. This change is low-risk and should be transparent to users, with no functional or API changes expected.

Walkthrough

The PR updates an indirect Go module requirement in go.mod, replacing go.yaml.in/yaml/v2 v2.4.4 with go.yaml.in/yaml/v3 v3.0.4. No other module directives, direct dependencies, exported declarations, or source files were changed.

Changes

Dependency Update

Layer / File(s)	Summary
Module Requirement go.mod	Replaced indirect requirement go.yaml.in/yaml/v2 v2.4.4 with go.yaml.in/yaml/v3 v3.0.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks critical sections from the template including Issue link, Testing instructions, Reviewer notes, and the required Checklist, though it does provide dependency update details.	Add the missing template sections: link to the related issue (RHCLOUD-XXXXX), explain how to test locally, note any considerations for reviewers, and complete the required checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: updating the go.yaml.in/yaml dependency from v2 to v3, which matches the changeset perfectly.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

_{Review rate limit: 9/10 reviews remaining, refill in 6 minutes.}

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@go.mod`:
- Line 61: The go.mod contains two distinct module paths for the same YAML
library (go.yaml.in/yaml/v3 v3.0.4 and gopkg.in/yaml.v3 v3.0.1) causing
duplicate versions and potential type incompatibilities; resolve by either
updating dependent modules (e.g., bump github.com/oapi-codegen/oapi-codegen/v2
or others that pull gopkg.in/yaml.v3) to versions that depend on
go.yaml.in/yaml/v3, or add an explicit replace directive to unify the paths
(e.g., replace gopkg.in/yaml.v3 => go.yaml.in/yaml/v3) in go.mod so both import
paths resolve to the same module version; ensure you run go mod tidy after the
change and verify tests/builds to confirm no breakage.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 9186e725-49ef-4a23-aedb-0d81f667b89f

📥 Commits

Reviewing files that changed from the base of the PR and between a43c18b and e1ab475.

📒 Files selected for processing (1)

• go.mod

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the dependency graph to identify what pulls in each yaml version

echo "=== Dependencies requiring gopkg.in/yaml.v3 ==="
go mod graph | grep 'gopkg.in/yaml.v3'

echo -e "\n=== Dependencies requiring go.yaml.in/yaml/v3 ==="
go mod graph | grep 'go.yaml.in/yaml/v3'

echo -e "\n=== Why gopkg.in/yaml.v3@v3.0.1 is needed ==="
go mod why gopkg.in/yaml.v3

echo -e "\n=== Why go.yaml.in/yaml/v3@v3.0.4 is needed ==="
go mod why go.yaml.in/yaml/v3

echo -e "\n=== Attempting to tidy and verify ==="
go mod tidy
echo "After tidy, checking for remaining duplicates:"
grep -n "yaml.v3" go.mod || echo "No yaml.v3 found after tidy"

Repository: RedHatInsights/quickstarts

Length of output: 5267

---

Duplicate yaml.v3 dependency versions persisting in go.mod.

Lines 61 and 70 both declare yaml.v3 dependencies at different versions: go.yaml.in/yaml/v3 v3.0.4 and gopkg.in/yaml.v3 v3.0.1. While these import paths refer to the same upstream library, Go treats them as separate module paths. The presence of both versions persists even after go mod tidy, indicating that different dependencies in the tree explicitly require these versions—go.yaml.in/yaml/v3@v3.0.4 is pulled by github.com/onsi/gomega@v1.39.1, while gopkg.in/yaml.v3@v3.0.1 is pulled by github.com/oapi-codegen/oapi-codegen/v2 and others. This can cause subtle type incompatibilities if code from packages using different import paths interacts.

To resolve, consider:

• Updating dependencies that pull gopkg.in/yaml.v3@v3.0.1 to versions that use go.yaml.in/yaml/v3 instead, or
• Adding an explicit replace directive in go.mod to alias one import path to the other (e.g., replace gopkg.in/yaml.v3 => go.yaml.in/yaml/v3), or
• Investigating whether all dependencies can be updated to standardize on the canonical go.yaml.in/yaml/v3 import path.

Also applies to: 70-70

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@go.mod` at line 61, The go.mod contains two distinct module paths for the
same YAML library (go.yaml.in/yaml/v3 v3.0.4 and gopkg.in/yaml.v3 v3.0.1)
causing duplicate versions and potential type incompatibilities; resolve by
either updating dependent modules (e.g., bump
github.com/oapi-codegen/oapi-codegen/v2 or others that pull gopkg.in/yaml.v3) to
versions that depend on go.yaml.in/yaml/v3, or add an explicit replace directive
to unify the paths (e.g., replace gopkg.in/yaml.v3 => go.yaml.in/yaml/v3) in
go.mod so both import paths resolve to the same module version; ensure you run
go mod tidy after the change and verify tests/builds to confirm no breakage.