feat(go): update github.com/pb33f/libopenapi-validator (v0.13.3 → v0.14.0)#163
Open
lrstanley-x[bot] wants to merge 1 commit into
Open
feat(go): update github.com/pb33f/libopenapi-validator (v0.13.3 → v0.14.0)#163lrstanley-x[bot] wants to merge 1 commit into
lrstanley-x[bot] wants to merge 1 commit into
Conversation
…14.0) Signed-off-by: lrstanley-x[bot] <153159847+lrstanley-x[bot]@users.noreply.github.com>
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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.
This PR contains the following updates:
v0.13.3→v0.14.0Release Notes
pb33f/libopenapi-validator (github.com/pb33f/libopenapi-validator)
v0.14.0Compare Source
Add kin-openapi parity features: router, content validation, and OpenAPI 3.2 support
Port key kin-openapi capabilities into libopenapi-validator:
v0.13.13Compare Source
Fixed slowdown in new
$defschema resource composition at scale, by using a cache, which needs lifecycle management, so in comes theRelease()pattern fromlibopenapi.Also reorders a prop in a struct, because it was creating a build issue downstream.
@siretart
v0.13.12Compare Source
bumps to yaml RC6, fixing a bunch of panics across the stack.
v0.13.11Compare Source
Circular refs supported in schema validation.
Circular references were never allowed in schema validation because the work required to bring references in line was too great. There have been many advances in libopenapi recently that have made this easier.
So, now the schema validator will build all references as inline resources first. This would have been too much work a year ago, but here we are.
Addresses issues #290 an #287
v0.13.10Compare Source
Fixes #281, fixes tests in from libopenapi bump and moves to our own fork of testify.
v0.13.9Compare Source
v0.13.8Compare Source
Reworked request and response schema validation to use errors.As instead of direct JSON Schema error type assertions, making validation error handling safer when errors are wrapped.
Fixed a goroutine leak in schema-property lookup for empty JSONPath values and added a regression test for that case.
@SebTardif
v0.13.7Compare Source
Fixes a few issues.
v0.13.6Compare Source
Fixes issues #83 (an oldie!)
v0.13.5Compare Source
Addresses
@vmarceau
v0.13.4Compare Source
Add opt-in readOnly/writeOnly rejection to strict mode
When
StrictRejectReadOnlyis enabled, readOnly properties in requests are reported as validation errors instead of being silently skipped. WhenStrictRejectWriteOnlyis enabled,writeOnlyproperties in responses are reported similarly.Addresses #90
@byted
Configuration
📅 Schedule: (in timezone America/Denver)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
PR generated using automation.