-
Notifications
You must be signed in to change notification settings - Fork 41
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
Bump yaml versions to gopkg.in/yaml.v3 #262
Conversation
Signed-off-by: Evan Lezar <[email protected]>
Signed-off-by: Evan Lezar <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we then tag a v1.0.1 ?
Given that this is causing issues in containerd and buildkit (moby/buildkit#5856) that may be useful. Using a replace rule pointing at these changes we see:
And updating the vendoring:
|
For
And after vendoring:
Showing the removal of the |
I have created #263 to track the release. |
Yes, I think tagging a v1.0.1 is mostly relevant to containerd/main vendoring footprint. There we were to ones forcing in yaml.v2 and this was a bit frowned upon, although not prohibitively much. |
I found this from podman where I also noticed the yaml.v2 causing new bloat. So I would very much appreciate the update to gopkg.in/yaml.v3 as well. |
This change updates the sigs.k8s.io/yaml version from v1.3.0 to v1.4.0 and switches to using gopkg.in/yaml.v3 for ordered YAML output. This means that consumers no longer need to pull in two YAML dependencies (v2 and v3).
See: