chore(deps): update module go.yaml.in/yaml/v2 to v3#975
chore(deps): update module go.yaml.in/yaml/v2 to v3#975red-hat-konflux[bot] wants to merge 1 commit intomainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: red-hat-konflux[bot] The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
WalkthroughUpdated an indirect YAML dependency in the Go module file from version v2 to v3, replacing Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
|
Hi @red-hat-konflux[bot]. Thanks for your PR. I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
aa20f71 to
7862549
Compare
7862549 to
9c73379
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
9c73379 to
c0af4b1
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@go.mod`:
- Around line 147-148: The go.mod contains a duplicate indirect require for
module go.yaml.in/yaml/v3 v3.0.4; remove the redundant require line so only a
single go.yaml.in/yaml/v3 v3.0.4 entry remains, then run `go mod tidy` to
normalize and update the module graph; look for the duplicate require entries
for go.yaml.in/yaml/v3 in the go.mod and delete one, saving the file and running
`go mod tidy` to ensure go.sum and formatting are corrected.
| go.yaml.in/yaml/v3 v3.0.4 // indirect | ||
| go.yaml.in/yaml/v3 v3.0.4 // indirect |
There was a problem hiding this comment.
Remove the duplicate go.yaml.in/yaml/v3 require entry.
There are two identical indirect requires for go.yaml.in/yaml/v3 v3.0.4. Keep a single entry and run go mod tidy to normalize the file.
♻️ Proposed fix
- go.yaml.in/yaml/v3 v3.0.4 // indirect
go.yaml.in/yaml/v3 v3.0.4 // indirect📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| go.yaml.in/yaml/v3 v3.0.4 // indirect | |
| go.yaml.in/yaml/v3 v3.0.4 // indirect | |
| go.yaml.in/yaml/v3 v3.0.4 // indirect |
🤖 Prompt for AI Agents
In `@go.mod` around lines 147 - 148, The go.mod contains a duplicate indirect
require for module go.yaml.in/yaml/v3 v3.0.4; remove the redundant require line
so only a single go.yaml.in/yaml/v3 v3.0.4 entry remains, then run `go mod tidy`
to normalize and update the module graph; look for the duplicate require entries
for go.yaml.in/yaml/v3 in the go.mod and delete one, saving the file and running
`go mod tidy` to ensure go.sum and formatting are corrected.
|
@red-hat-konflux[bot]: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This PR contains the following updates:
v2.4.3->v3.0.4Warning
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.4Compare Source
v3.0.3Compare Source
v3.0.2Compare Source
v3.0.1Compare Source
v3.0.0Compare 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.
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.