Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump github.com/pb33f/libopenapi from 0.16.13 to 0.18.4 #213

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 21, 2024

Bumps github.com/pb33f/libopenapi from 0.16.13 to 0.18.4.

Release notes

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

v0.18.4

Added GetIndex() and GetContext() to v3 low models.

Makes it much easier for downstream tools to know all the things

fix: indexing of operations which are $refs (#339)

Why We have a linting rule which checks for duplicate operation IDs / duplicate operations. This linting rule wasn't catching duplicates if the operations were living in an external $ref.

What Currently when building the index of operations we weren't checking for refs, this PR changes that.

@​mfbx9da4

v0.18.3

This fixes vacuum rules that lookup operations in the index where:

The original spec (root.yaml) has an external reference to a file in a different directory ./paths/mypath.yaml In that location, there is a relative reference to a path-item in a nearby file, e.g. ./components.yaml#/path-item What was previously happening in [2] is that the ./components.yaml was being resolved in ./components.yaml (the parent directory) instead of ./paths/components.yaml (the right directory). This resulted in a failure to evaluate path item references and unexpected linting failures.

This changes adjusts the lookup to search through the index's nodeMap to find the location of the YAML $ref node value that's been evaluated. Once we find it, we lookup the associated index of that file and do a seek in that specific index.

We also fix a race condition with resolving the specification asyncronously -- if we are going to an external ref we must do it sequentially as otherwise an index might be added multiple times during an async FindComponent call. This latent bug was exposed as we tested this.

@​ThomasRooney

v0.18.1

Fixes a small off by one error in the resolver.

Also adds extension support to server variables that was missing, courtesy of @​geffersonFerraz

v0.18.0

Fixes some memory issues with string allocations. Utility functions were causing a surge of memory when run repeatedly.

Also upgrades the rolodex to use the real name of the root file, instead of 'root.yaml'

Fixes an error that was hard-coded into the License object. Also adds Extensions to License and Contact objects.

No breaking changes, no signature changes.,

@​lobocv

v0.17.0

Support for go 1.23 and the new range over function https://tip.golang.org/wiki/RangefuncExperiment feature.

A selection of new methods have been added to the orderedmap package.

  • FromOldest()

... (truncated)

Commits
  • 442ba3b bumped coverage
  • 7190897 bumped coverage again
  • 25a489e bumped code
  • 70e102f stupid context!
  • 90f476a Added GetIndex() and GetContext() to v3 low models.
  • aae2f92 return error if rendermap is nil
  • ebaa998 Added additional prop checks for renderer
  • 1aaceff fix: indexing of operations which are $refs
  • 5ababf2 chore: fix wiretap link in README
  • eff4ce8 chore: remove unused param from extractRequiredReferenceProperties
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [github.com/pb33f/libopenapi](https://github.com/pb33f/libopenapi) from 0.16.13 to 0.18.4.
- [Release notes](https://github.com/pb33f/libopenapi/releases)
- [Commits](pb33f/libopenapi@v0.16.13...v0.18.4)

---
updated-dependencies:
- dependency-name: github.com/pb33f/libopenapi
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Oct 21, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 24, 2024

Superseded by #217.

@dependabot dependabot bot closed this Oct 24, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/pb33f/libopenapi-0.18.4 branch October 24, 2024 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants