Repository navigation
chore(deps): bump libopenapi to v0.41.5 - #4554
Merged
Merged
Conversation
Introduce a small nodeDecoder interface so yamlNodeToValue no longer depends on a concrete yaml.Node type, letting it work across old and new YAML node implementations. Assisted-By: docker-agent Signed-off-by: David Gageot <david.gageot@docker.com>
Pulls in updated jsonpath and ordered-map deps. Signed-off-by: David Gageot <david.gageot@docker.com> Assisted-By: docker-agent
aheritier
added
area/deps
gtardif
approved these changes
Oct 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 8, 2026
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
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.
github.com/pb33f/libopenapiv0.41.5 ships a new YAML fork, and the previousopenapi.gocode decoded nodes by depending directly on the concreteyaml.Nodetype. Bumping straight to the new version would have caused a node type mismatch at decode time, so the upgrade needed a small refactor first.yamlNodeToValuenow decodes through a tinynodeDecoderinterface (Decode(target any) error) instead of importing either YAML library directly. Callers provide a fallback that preserves typed values and the raw string when decoding fails, and the existing nil guards are unchanged. With that in place,go.modmovesgithub.com/pb33f/libopenapifrom v0.40.0 to v0.41.5, pulling in updatedjsonpathandordered-maptransitive versions;go.yaml.in/yaml/v4stays indirect because ofgo-vcr, andpb33f/go-yamlv0.1.1 is added as indirect. No other direct dependencies or replacement pins change.Test coverage was extended with a fake decoder exercising successful types, null, and partial-output errors, plus integration cases for enum, default float, boolean, null, array, and object values; existing string and integer tests were kept as-is.
task build,task test, andtask lintall pass, matching CI's golangci-lint v2.13.2, and the unchanged go-licenses v1.6.0 Linux/amd64 check still passes since no license-affecting dependency changed.