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

Migrate to gopkg.in/yaml.v3 #37553

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

L3n41c
Copy link

@L3n41c L3n41c commented Jan 28, 2025

Description

Migrate from gopkg.in/yaml.v2 to gopkg.in/yaml.v3.
Some modules were already pulling the two versions and moving to v3 helped removing one of the two for some of them.

@songy23 songy23 added dependencies Pull requests that update a dependency file Skip Changelog PRs that do not require a CHANGELOG.md entry labels Jan 28, 2025
Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

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

Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@andrzej-stencel andrzej-stencel left a comment

Choose a reason for hiding this comment

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

I'm trying to understand the implications of this change, given that moving from yaml.v2 to yaml.v3 does have some breaking changes https://ubuntu.com/blog/api-v3-of-the-yaml-package-for-go-is-available. Examples: not allowing integers for durations, enforcing unique keys. They are probably not common, but still may cause errors for configurations that previously did not error out.

If I understand correctly, this PR introduces potentially functional changes to the following components:

Ideally this should be carefully considered by the code owners

Please correct me if I'm missing something and the impact of this change is not as I'm seeing it.

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.

5 participants