chore: Upgrade from yaml v2 to v3 everywhere #9279
Merged
Conversation
This file contains 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
mangalaman93
previously approved these changes
Jan 16, 2025
|
@RJKeevil could you rebase on latest main please? |
|
@mangalaman93 Done! |
|
@mangalaman93 looks like the failure this time was just infra related, probably retriggering the job would work? The self-hosted runner: warp-4x-x64-wvnb41gx4zlj0vkx lost communication with the server. |
|
Rebased and pushed again to retrigger the tests, look good now |
mangalaman93
approved these changes
Jan 28, 2025
|
Thank you for the PR @RJKeevil! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Upgraded gopkg.in/yaml from v2 to v3 in all places. Mostly this is for housekeeping and to bring our fork more in line with main, so that we may remove the fork in near future.
Checklist