🌱 deps: switch from gopkg.in/yaml.vX to go.yaml.in/yaml/vX #4895
Conversation
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
scop
requested review from
raghavkaul and
spencerschrock
and removed request for
a team
dosubot
bot
added
the
size:S
scop
temporarily deployed
to
integration-test
GitHub Actions
Inactive
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4895 +/- ##
==========================================
+ Coverage 66.80% 69.70% +2.89%
==========================================
Files 230 251 +21
Lines 16602 15649 -953
==========================================
- Hits 11091 10908 -183
+ Misses 4808 3867 -941
- Partials 703 874 +171 🚀 New features to boost your workflow:
|
Contributor
|
Could you sign the DCO? |
The latter is a maintained fork of the former. https://github.com/yaml/go-yaml#project-status While at it, upgrade from 2.4.0 to 2.4.2 and 3.0.1 to 3.0.4, these were already indirectly used. 2.4.0 are identical, 2.4.0...2.4.1 diff: https://gist.github.com/scop/57f94f2bf97fb6a2d01349fa59d88530 3.0.1 are identical, 3.0.1..3.0.2 diff: https://gist.github.com/scop/57f94f2bf97fb6a2d01349fa59d88530 Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
Contributor
Author
|
Oops, sorry, done. |
spencerschrock
approved these changes
Jan 8, 2026
Member
spencerschrock
left a comment
spencerschrock
left a comment
There was a problem hiding this comment.
Thanks. We should probably merge all of our yaml usage to the same version at some point. Whether that's v3 or v4.
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.
What kind of change does this PR introduce?
Dependency health improvement.
What is the current behavior?
Use of unmaintained gopkg.in/yaml.vX dependencies.
What is the new behavior (if this is a feature change)?**
Use of maintained go.yaml.in/yaml/vX dependencies.
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
https://github.com/yaml/go-yaml#project-status
While at it, upgrade from 2.4.0 to 2.4.2 and 3.0.1 to 3.0.4, these were already indirectly used.
2.4.0 are identical, 2.4.0...2.4.1 diff: https://gist.github.com/scop/57f94f2bf97fb6a2d01349fa59d88530
3.0.1 are identical, 3.0.1..3.0.2 diff: https://gist.github.com/scop/57f94f2bf97fb6a2d01349fa59d88530
Remaining diffs as usual at https://github.com/yaml/go-yaml/tags
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note(In particular, describe what changes users might need to make in their
application as a result of this pull request.)