Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 12, 2025

This PR contains the following updates:

Package Change Age Confidence
gopkg.in/yaml.v2 v2.4.0 -> v3.0.1 age confidence

Release Notes

go-yaml/yaml (gopkg.in/yaml.v2)

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch 2 times, most recently from f5154a1 to 1945ac7 Compare August 19, 2025 12:57
Copy link
Contributor

@cardoe cardoe left a comment

Choose a reason for hiding this comment

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

This seems wrong for what the update is claiming.

@renovate renovate bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch from 1945ac7 to eb5d07b Compare September 3, 2025 12:48
@renovate
Copy link
Contributor Author

renovate bot commented Sep 10, 2025

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.

@renovate renovate bot deleted the renovate/gopkg.in-yaml.v2-3.x branch September 10, 2025 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants