Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update module gopkg.in/yaml.v2 to v3 #390

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ethpandaops-renovatebot[bot]
Copy link
Contributor

@ethpandaops-renovatebot ethpandaops-renovatebot bot commented Oct 8, 2024

This PR contains the following updates:

Package Type Update Change
gopkg.in/yaml.v2 require major v2.4.0 -> v3.0.1

Release Notes

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

v3.0.1

Compare Source

v3.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "every 2 weeks on Tuesday" in timezone Europe/Berlin, Automerge - "after 9am every weekday except Friday or Monday,before 11am every weekday except Friday or Monday" in timezone Europe/Berlin.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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.

@ethpandaops-renovatebot ethpandaops-renovatebot bot force-pushed the renovate/gopkg.in-yaml.v2-3.x branch from 7aac7a3 to b520f3b Compare December 10, 2024 01:34
@ethpandaops-renovatebot
Copy link
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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

Successfully merging this pull request may close these issues.

2 participants