Update module go.yaml.in/yaml/v2 to v2.4.4

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
go.yaml.in/yaml/v2	v2.4.3 → v2.4.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)

v2.4.4

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.

Summary by CodeRabbit

• Chores
  • Updated YAML library dependency to the latest version.

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: e78ee105-b97d-4a7e-8888-336e0e8db218

📥 Commits

Reviewing files that changed from the base of the PR and between cecd5f2 and 32c0497.

⛔ Files ignored due to path filters (2)

• go.sum is excluded by !**/*.sum
• vendor/modules.txt is excluded by !vendor/**, !**/vendor/**

📒 Files selected for processing (1)

• go.mod

---

📝 Walkthrough

Walkthrough

The pull request updates a single indirect dependency in the go module file. The indirect dependency go.yaml.in/yaml/v2 is bumped from version v2.4.3 to v2.4.4. This is a patch-level version update to an existing transitive dependency and does not affect any direct module imports or exported public entities.

🚥 Pre-merge checks | ✅ 10 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is largely incomplete compared to the required template, missing critical sections like detailed issue description, type classification, testing steps, and verification checklist.	Complete the PR description by selecting a type (likely 'build' or 'chore'), adding issue/testing details, and checking the developer verification checklist items.
Ipv6 And Disconnected Network Test Compatibility	⚠️ Warning	New Ginkgo e2e tests contain hardcoded IPv4 addresses. dummy_test.go uses 10.0.0.0/16, test_rosacli_cluster.go uses 192.168.1.0/23 and 10.0.0.1. Tests will fail in IPv6-only disconnected environments.	Update tests to support IPv6: use GetIPAddressFamily() to detect cluster family, correctCIDRFamily() to select CIDR, or InIPv4ClusterContext() to skip on IPv6.

✅ Passed checks (10 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: updating the go.yaml.in/yaml/v2 module to v2.4.4.
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 updates go.yaml.in/yaml/v2 to v2.4.4. Analyzed all 2,645 Ginkgo test names - all use static strings with no fmt.Sprintf, concatenation, UUIDs, timestamps, or generated identifiers.
Test Structure And Quality	✅ Passed	Initial commit updating go.yaml.in/yaml/v2 dependency version. Test files are being added, not modified. Ginkgo test code quality check is not applicable to dependency updates.
Microshift Test Compatibility	✅ Passed	Check not applicable. This is openshift/rosa (CLI tool), not openshift/origin. Tests are CLI-based, not cluster API tests requiring MicroShift compatibility.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo e2e tests added. PR only updates go.yaml.in/yaml/v2 dependency from v2.4.3 to v2.4.4. SNO test compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR is a routine dependency update (go.yaml.in/yaml/v2 v2.4.3→v2.4.4). Contains no deployment manifests, operator code, controllers, or scheduling constraints. Check is not applicable.
Ote Binary Stdout Contract	✅ Passed	PR only updates go.yaml.in/yaml/v2 from v2.4.3 to v2.4.4 in go.mod/go.sum. No source code (.go files) were modified. No stdout writes to process-level code introduced.

_{✏️ 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/master/go.yaml.in-yaml-v2-2.x

---

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

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