Skip to content

Update module go.yaml.in/yaml/v2 to v3#1637

Open
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x
Open

Update module go.yaml.in/yaml/v2 to v3#1637
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x

Conversation

@red-hat-konflux
Copy link
Copy Markdown
Contributor

@red-hat-konflux red-hat-konflux Bot commented May 14, 2026

This PR contains the following updates:

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

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 red-hat-konflux Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels May 14, 2026
@openshift-ci openshift-ci Bot requested review from raptorsun and xrajesh May 14, 2026 20:19
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD e95793d and 2 for PR HEAD 1772cf9 in total

@red-hat-konflux red-hat-konflux Bot changed the title Update module go.yaml.in/yaml/v2 to v3 Update module go.yaml.in/yaml/v2 to v3 - autoclosed May 16, 2026
@red-hat-konflux red-hat-konflux Bot closed this May 16, 2026
@red-hat-konflux red-hat-konflux Bot deleted the konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x branch May 16, 2026 04:21
@red-hat-konflux red-hat-konflux Bot changed the title Update module go.yaml.in/yaml/v2 to v3 - autoclosed Update module go.yaml.in/yaml/v2 to v3 May 16, 2026
@red-hat-konflux red-hat-konflux Bot reopened this May 16, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x branch 2 times, most recently from 1772cf9 to 39547f3 Compare May 16, 2026 08:32
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 16, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 16, 2026

New changes are detected. LGTM label has been removed.

@red-hat-konflux red-hat-konflux Bot changed the title Update module go.yaml.in/yaml/v2 to v3 Update module go.yaml.in/yaml/v2 to v3 - autoclosed May 19, 2026
@red-hat-konflux red-hat-konflux Bot closed this May 19, 2026
@red-hat-konflux red-hat-konflux Bot changed the title Update module go.yaml.in/yaml/v2 to v3 - autoclosed Update module go.yaml.in/yaml/v2 to v3 May 19, 2026
@red-hat-konflux red-hat-konflux Bot reopened this May 19, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x branch 2 times, most recently from 39547f3 to de59261 Compare May 19, 2026 17:49
@raptorsun
Copy link
Copy Markdown
Contributor

/hold
breaking change

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 26, 2026
@red-hat-konflux red-hat-konflux Bot changed the title Update module go.yaml.in/yaml/v2 to v3 Update module go.yaml.in/yaml/v2 to v3 - autoclosed May 28, 2026
@red-hat-konflux red-hat-konflux Bot closed this May 28, 2026
@red-hat-konflux red-hat-konflux Bot changed the title Update module go.yaml.in/yaml/v2 to v3 - autoclosed Update module go.yaml.in/yaml/v2 to v3 May 28, 2026
@red-hat-konflux red-hat-konflux Bot reopened this May 28, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x branch from de59261 to ac7a7ad Compare May 28, 2026 04:16
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 28, 2026

📝 Walkthrough

Walkthrough

The PR updates the Go module manifest to replace the indirect YAML dependency go.yaml.in/yaml/v2 v2.4.4 with go.yaml.in/yaml/v3 v3.0.4 in go.mod.

Changes

YAML Library Upgrade

Layer / File(s) Summary
Update indirect YAML require
go.mod
Replaces go.yaml.in/yaml/v2 v2.4.4 with go.yaml.in/yaml/v3 v3.0.4 in the indirect require list.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • xrajesh
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Update module go.yaml.in/yaml/v2 to v3' directly and clearly summarizes the main change - updating a YAML dependency from v2 to v3, which is the only modification in the changeset.
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@go.mod`:
- Around line 108-109: go.mod contains a duplicated module requirement
"go.yaml.in/yaml/v3 v3.0.4 // indirect"; remove one of the identical lines so
the dependency appears only once and then run go mod tidy to ensure the module
file is normalized; target the duplicate "go.yaml.in/yaml/v3 v3.0.4 // indirect"
entry when editing.
🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: c84fc84e-2061-4ad5-acd8-eebd226383f4

📥 Commits

Reviewing files that changed from the base of the PR and between 15eaec5 and ac7a7ad.

📒 Files selected for processing (1)
  • go.mod

Comment thread go.mod
Comment on lines +108 to 109
go.yaml.in/yaml/v3 v3.0.4 // indirect
go.yaml.in/yaml/v3 v3.0.4 // indirect
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify duplicate go.yaml.in/yaml/v3 entries in go.mod
rg -n '^\s*go\.yaml\.in/yaml/v3\s+v3\.0\.4\b' go.mod
# Expected: exactly one match. Current diff shows two (Lines 108 and 109).

Repository: openshift/lightspeed-operator

Length of output: 159


Remove duplicated go.yaml.in/yaml/v3 v3.0.4 // indirect entries from go.mod.
go.mod contains the exact same go.yaml.in/yaml/v3 v3.0.4 // indirect requirement twice (lines 108–109); keep only one to avoid go.mod hygiene/tooling issues.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` around lines 108 - 109, go.mod contains a duplicated module
requirement "go.yaml.in/yaml/v3 v3.0.4 // indirect"; remove one of the identical
lines so the dependency appears only once and then run go mod tidy to ensure the
module file is normalized; target the duplicate "go.yaml.in/yaml/v3 v3.0.4 //
indirect" entry when editing.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/main/go.yaml.in-yaml-v2-3.x branch from ac7a7ad to 21a449f Compare May 28, 2026 08:21
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 28, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 28, 2026

@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/images 21a449f link true /test images
ci/prow/ci-index-lightspeed-bundle-test 21a449f link true /test ci-index-lightspeed-bundle-test
ci/prow/fips-image-scan-operator 21a449f link true /test fips-image-scan-operator
ci/prow/unit 21a449f link true /test unit
ci/prow/bundle-e2e-4-21 21a449f link true /test bundle-e2e-4-21
ci/prow/generate 21a449f link true /test generate

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant