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

fix(deps): update fury-adapter-swagger requirement from 0.27.1 to 0.27.2 #329

Merged

Conversation

dependabot-preview[bot]
Copy link
Contributor

Updates the requirements on fury-adapter-swagger to permit the latest version.

Release notes

Sourced from fury-adapter-swagger's releases.

fury-adapter-swagger 0.27.2

Bug Fixes

  • Prevents a 'Path Item Object' from being included in a Resource Group created by an 'Operation Object' in a previously defined 'Path Item Object'.

  • Optional parameters will now include an optional typeAttribute in the parse result. This will fix conversion to API Blueprint with fury-cli where optional parameters have shown up as required in the generated API Blueprint.

  • Allows generating of JSON bodies for schemas which make use of allOf and include circular references. Under some circumstances this would previously fail, and a warning may have been emitted "Unable to generate application/json example message body out of JSON Schema"

Changelog

Sourced from fury-adapter-swagger's changelog.

0.27.2 (2019-08-08)

Bug Fixes

  • Prevents a 'Path Item Object' from being included in a Resource Group created
    by an 'Operation Object' in a previously defined 'Path Item Object'.

  • Optional parameters will now include an optional typeAttribute in the parse
    result. This will fix conversion to API Blueprint with fury-cli where
    optional parameters have shown up as required in the generated API Blueprint.

  • Allows generating of JSON bodies for schemas which make use of allOf and
    include circular references. Under some circumstances this would previously
    fail, and a warning may have been emitted "Unable to generate
    application/json example message body out of JSON Schema"

0.27.1 (2019-06-03)

Bug Fixes

  • Fixes a problem while parsing a document which contains a Swagger Schema for
    a string which contains both a minLength and a pattern property which are
    incompatible. For example, the following pattern: ^[A-z]*$ which is making
    use of * which means that it allows strings that are zero length or more.
    If there is a property minLength which is incompatible with the pattern
    such as if minLength is set to 1. Previously this would cause the parser to
    get into an infinite loop.

0.26.0 (2019-06-11)

Breaking

  • Support for NodeJS 6 has been removed, upgrading to NodeJS 8 or newer is
    recommended.

Bug Fixes

  • JSON value generation will now support schemas which contain an array of objects.
    For example, the following schema:

    type: array
    items:
      type: object
      properties:
        name:
          type: string
          example: doe
... (truncated)
Commits
  • 35f97c5 chore(project): release
  • f8d2939 fix(oas2): allow circular references in allOf
  • 0288e87 fix(oas2): add optional typeAttribute for optional parameters
  • 95896b6 fix(oas2): prevent resource ending up in previous resource group
  • d9146d0 chore(deps): bump z-schema from 3.25.1 to 4.1.0
  • dfb943c chore(deps): bump swagger-parser from 6.0.5 to 8.0.0
  • b65ec57 refactor(oas2): use provided index from forEach
  • 2d0691c chore(core): explicitly define package files
  • See full diff 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 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)
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Aug 8, 2019
@honzajavorek honzajavorek merged commit da8288b into master Aug 8, 2019
@dependabot-preview dependabot-preview bot deleted the dependabot/npm_and_yarn/fury-adapter-swagger-0.27.2 branch August 8, 2019 17:35
@ApiaryBot
Copy link
Collaborator

🎉 This PR is included in version 9.0.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

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 released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants