Skip to content

feat(go): update github.com/pb33f/libopenapi-validator (v0.10.2 → v0.11.4)#130

Open
lrstanley-x[bot] wants to merge 1 commit intomasterfrom
renovate/github.com-pb33f-libopenapi-validator-0.x
Open

feat(go): update github.com/pb33f/libopenapi-validator (v0.10.2 → v0.11.4)#130
lrstanley-x[bot] wants to merge 1 commit intomasterfrom
renovate/github.com-pb33f-libopenapi-validator-0.x

Conversation

@lrstanley-x
Copy link
Contributor

@lrstanley-x lrstanley-x bot commented Feb 1, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/pb33f/libopenapi-validator v0.10.2 -> v0.11.4 age adoption passing confidence

Release Notes

pb33f/libopenapi-validator (github.com/pb33f/libopenapi-validator)

v0.11.4

Compare Source

Adds lazy context tracking to speed up path searches a little. No new features, no other fixes.

v0.11.3

Compare Source

Adds a fix for nullable enum validation and moves HEAD validation to be RFC 7231 Section 4.3.2 compliant.

@​k2tzumi, @​saisatishkarra

v0.11.2

Compare Source

Fixed some caching issues with long-running processes, no new features.

v0.11.1

Compare Source

Handles nullable + allOf edge cases, and bumps libopenapi to v0.33.1

@​alexrjones

v0.11.0

Compare Source

Upgrades to libopenapi v0.33.0 and implements new faster and improved hashing.

Adds some node caching, retains validator options and refactors some constants, fixes a nil pointer. Addresses #​223

@​its-hammer-time @​Nivl


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, check this box

PR generated using automation.

@lrstanley-x lrstanley-x bot requested a review from lrstanley February 1, 2026 05:28
@codecov
Copy link

codecov bot commented Feb 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.23%. Comparing base (07961d7) to head (81207f8).
⚠️ Report is 7 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #130      +/-   ##
==========================================
- Coverage   69.37%   69.23%   -0.14%     
==========================================
  Files          10       10              
  Lines        2436     2022     -414     
==========================================
- Hits         1690     1400     -290     
+ Misses        632      508     -124     
  Partials      114      114              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

…11.4)

Signed-off-by: lrstanley-x[bot] <153159847+lrstanley-x[bot]@users.noreply.github.com>
@lrstanley-x lrstanley-x bot force-pushed the renovate/github.com-pb33f-libopenapi-validator-0.x branch from 97db9b1 to 81207f8 Compare February 15, 2026 05:27
@lrstanley-x lrstanley-x bot changed the title feat(go): update github.com/pb33f/libopenapi-validator (v0.10.2 → v0.11.0) feat(go): update github.com/pb33f/libopenapi-validator (v0.10.2 → v0.11.4) Feb 15, 2026
@lrstanley-x
Copy link
Contributor Author

lrstanley-x bot commented Feb 15, 2026

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 2 additional dependencies were updated

Details:

Package Change
github.com/pb33f/jsonpath v0.7.1 -> v0.8.1
github.com/pb33f/libopenapi v0.33.0 -> v0.33.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants