🐛Remove gopkg.in/yaml.v2 and migrate usage to gopkg.in/yaml.v3#1415
🐛Remove gopkg.in/yaml.v2 and migrate usage to gopkg.in/yaml.v3#1415chimanjain wants to merge 1 commit into
Conversation
|
Welcome @chimanjain! |
|
Hi @chimanjain. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: chimanjain The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: Chiman Jain <chimanjain15@gmail.com>
c6d5eed to
74f1eaa
Compare
Remove
gopkg.in/yaml.v2and migrate usage togopkg.in/yaml.v3Currently we are using both
gopkg.in/yaml.v2andgopkg.in/yaml.v3, which may lead to inconsistency in it's behavior. This will help bring closure to the above issue.