Repository navigation
build(deps): bump go.yaml.in/yaml/v4 to v4.0.0 - #991
Merged
Merged
Conversation
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
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
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 this PR does, in one sentence
Bumps
go.yaml.in/yaml/v4fromv4.0.0-rc.4to the finalv4.0.0release, published on November 4, 2026.Context
compose-go pinned a release candidate of go-yaml v4 while the stable release was pending. The test PRs on
v4.0.0-rc.8(#981) andv4.0.0-rc.9(#987) established that the only blocker was a regression inNode.Decode, which stopped applying go-yaml's default alias and depth limits (so the alias-bomb test never returned); it was fixed upstream in rc.9 (yaml/go-yaml#475) and no workaround is needed inResetProcessor.What the PR brings
Only the
go.mod/go.sumbump, with no change in the loader. The full suite passes, includingTestAliasBombPrevented. The changes between rc.9 and v4.0.0 are limited to the removal of the already-deprecatedLimitplugin API (which compose-go does not use), a YAML test-suite comparison fix and documentation, so there is no impact on marshalling, anchors and merge keys, error messages or node positions.Compose builds compose-go with the go-yaml version selected in its own module, so the matching docker/compose bump follows separately.
🤖 Generated with Claude Code