Skip to content
New issue

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

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

Already on GitHub? # to your account

Update swagger parser to the latest stable version v2.0.16 #4550

Merged
merged 1 commit into from
Nov 20, 2019

Conversation

wing328
Copy link
Member

@wing328 wing328 commented Nov 20, 2019

Update swagger parser to the latest stable version

Ref: https://github.com/swagger-api/swagger-parser/releases/tag/v2.0.16

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project before.
  • Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
  • File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

cc @OpenAPITools/generator-core-team

@wing328 wing328 added this to the 4.2.2 milestone Nov 20, 2019
@wing328 wing328 merged commit e4364b6 into master Nov 20, 2019
@wing328 wing328 deleted the swagger-parser-update branch November 20, 2019 08:54
@wing328 wing328 changed the title Update swagger parser to the latest stable version Update swagger parser to the latest stable version v2.0.16 Dec 2, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant