Skip to content

chore(deps): update module go.yaml.in/yaml/v2 to v3 (9.4)#4782

Closed
elastic-renovate-prod[bot] wants to merge 1 commit into9.4from
renovate/9.4-go.yaml.in-yaml-v2-3.x
Closed

chore(deps): update module go.yaml.in/yaml/v2 to v3 (9.4)#4782
elastic-renovate-prod[bot] wants to merge 1 commit into9.4from
renovate/9.4-go.yaml.in-yaml-v2-3.x

Conversation

@elastic-renovate-prod
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
go.yaml.in/yaml/v2 indirect major v2.4.4 -> v3.0.4

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard 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 - "* 1 * * 1-5" (UTC), 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

This PR has been generated by Renovate Bot.

@elastic-renovate-prod elastic-renovate-prod Bot added backport-skip dependencies Pull requests that update a dependency file renovate Team:Security-Cloud Services Security Data Experience - Cloud Services team. labels Apr 17, 2026
@elastic-renovate-prod elastic-renovate-prod Bot requested a review from a team as a code owner April 17, 2026 03:21
@elastic-renovate-prod elastic-renovate-prod Bot added backport-skip dependencies Pull requests that update a dependency file renovate labels Apr 17, 2026
@elastic-renovate-prod
Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact 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 -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go: go.yaml.in/yaml/v2/v3@v3.0.4: unrecognized import path "go.yaml.in/yaml/v2/v3": reading https://go.yaml.in/yaml/v2/v3?go-get=1: 404 Not Found

@elastic-renovate-prod elastic-renovate-prod Bot added the Team:Security-Cloud Services Security Data Experience - Cloud Services team. label Apr 17, 2026
@elastic-renovate-prod elastic-renovate-prod Bot force-pushed the renovate/9.4-go.yaml.in-yaml-v2-3.x branch from ffdd6c9 to bab57e6 Compare April 17, 2026 07:17
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Apr 17, 2026

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b renovate/9.4-go.yaml.in-yaml-v2-3.x upstream/renovate/9.4-go.yaml.in-yaml-v2-3.x
git merge upstream/9.4
git push upstream renovate/9.4-go.yaml.in-yaml-v2-3.x

@elastic-renovate-prod elastic-renovate-prod Bot force-pushed the renovate/9.4-go.yaml.in-yaml-v2-3.x branch 4 times, most recently from 11dbb32 to 7e9cb23 Compare April 22, 2026 02:59
@jeniawhite jeniawhite enabled auto-merge (squash) April 22, 2026 04:56
Copy link
Copy Markdown
Contributor

@jeniawhite jeniawhite left a comment

Choose a reason for hiding this comment

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

LGTM - approving for auto-merge

@elastic-renovate-prod elastic-renovate-prod Bot force-pushed the renovate/9.4-go.yaml.in-yaml-v2-3.x branch from 7e9cb23 to 03a7c06 Compare April 22, 2026 06:50
@jeniawhite
Copy link
Copy Markdown
Contributor

Closing this PR as the module path change is incorrect. Renovate updated go.yaml.in/yaml/v2 to go.yaml.in/yaml/v2/v3 which is an invalid module path (returns 404 from the Go module proxy). The correct v3 module path is go.yaml.in/yaml/v3, which is already present in go.mod. The upgrade from v2 to v3 requires import path changes in consuming packages and cannot be done as a simple version bump.

@jeniawhite jeniawhite closed this Apr 22, 2026
auto-merge was automatically disabled April 22, 2026 14:11

Pull request was closed

@elastic-renovate-prod
Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@elastic-renovate-prod elastic-renovate-prod Bot deleted the renovate/9.4-go.yaml.in-yaml-v2-3.x branch April 22, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-skip dependencies Pull requests that update a dependency file renovate Team:Security-Cloud Services Security Data Experience - Cloud Services team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant