chore: move from gopkg.in/yaml.v3 to sigs.k8s.io/yaml/goyaml.v3#1727
Closed
wcrum wants to merge 1 commit into
Closed
chore: move from gopkg.in/yaml.v3 to sigs.k8s.io/yaml/goyaml.v3#1727wcrum wants to merge 1 commit into
wcrum wants to merge 1 commit into
Conversation
gopkg.in/yaml.v3 is unmaintained, move to sigs.k8s.io/yaml as primary maintained version
Collaborator
Collaborator
|
sigs.k8s.io/yaml is not in a better shape, maintenance wise. For example, my one year old pull request didn't get a review: kubernetes-sigs/yaml#110 So that library is not a good replacement. |
dolmen
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gopkg.in/yaml.v3 is unmaintained, move to sigs.k8s.io/yaml as primary maintained version
Summary
Simply modified reference of gopkg.in/yaml.v3 -> sigs.k8s.io/yaml which is a mainted fork of go-yaml.
Changes
Move from on yaml to another yaml provider. Think we can probably remove a lot of the additional comments.
Motivation
Unmaintained dependency poses risk.
Related issues
#1724
#1725
Closes #1724