Bump github.com/pb33f/libopenapi from 0.13.22 to 0.14.4

[dependabot]

Bumps github.com/pb33f/libopenapi from 0.13.22 to 0.14.4.

Release notes

Sourced from github.com/pb33f/libopenapi's releases.

v0.14.4

Removed the JSONParsingChannel concept completely.

It's the source of a number of problems, when it comes to multi-tenancy and race conditions. It's toast. Good riddance.

v0.14.3

Fixed issue reported in daveshanley/vacuum#400

Added a safety check to prevent an overflow. No new features.

v0.14.2

Fixes #215

v0.14.1

Fixes edge case in Schema() low level model that was not carrying through context correctly when building against exploded references.

Reported in #219

v0.14.0

A major update to libopenapi.

ALL maps are now ordered maps in the datamodel

This is a major breaking change to all users of the datamodel. Examples are now also exposed as raw *yaml.Node elements, vs any

Picks up from pb33f/libopenapi#138 and tries to address pb33f/libopenapi#119

• Support iterating through the high model in the same order as the OpenAPI document
• Render documents out deterministically
• Render documents out matching the original order (if just making light modifications to the document)
• Control the order of the rendered out docs, for example when the order of path items or components are specifically reordered
• Any maps stored within example or examples fields in schemas can maintain order both on read/write

@​TristanSpeakEasy @​Baliedge

Commits

• 08571b7 Removed JsonParsingChannel
• 3b88510 Added safety check for extracting refs from non-openapi files
• bc040de fixed formatting
• 961dca7 added test for schema type
• f67d666 Issue #214 cannot be re-created, added test to validate.
• 0b7f809 Added in high level schema type ref #215
• 9cf06d3 Fixed glitch reported by #219
• a912093 Merge pull request #205 from speakeasy-api/ordered-libopenapi
• f86d7bc Merge branch 'main' into ordered-libopenapi
• e4a6c65 chore: add more test coverage
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[austinvalle]

Handling in #111

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.