build: use yaml/go-yaml instead of unmaintained yaml.v3, fixes #7280#7381
Merged
build: use yaml/go-yaml instead of unmaintained yaml.v3, fixes #7280#7381
Conversation
|
Download the artifacts for this pull request:
See Testing a PR. |
Member
Author
|
Updated mergo to lose its dependency. The traditional module is still required by stretchr/testify, which is used in testcommon tests (assert) |
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
2 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.
The Issue
yaml/go-yaml seems to have reached some kind of maturity
How This PR Solves The Issue
Try it out.
Manual Testing Instructions
Look at test results. Use it. Tests should tell us everything.
Automated Testing Overview
Release/Deployment Notes