Releases: swagger-api/swagger-parser
2.0.3 - Failed release, please use `2.0.4`
Something went wrong with 2.0.3, please use swagger-parser 2.0.4 instead.
Swagger-parser 1.0.38 released!
Swagger-parser 2.0.4 released!
Notable Changes:
- Fix issue #811 OAS3 - RefResponse -> RefSchema external Resolving (#826)
- Decode properly refs (#824)
- Convert x-nullable for formData parameter (#821)
- Remove travis (#819)
- Fix NPE issue 813 OAS 3 (#816)
- Fix relative ref with http ref bug (#806)
- Test for Issue #799 OAS 3 (#802)
Known Issues:
- Not resolving relative ref in classpath from jar (WIP #700)
Swagger-parser 2.0.2 released!
Swagger-parser 2.0.2 released! 🎉
Notable Changes:
- Parsing of Extensions in Paths and Responses (#735 )
- Fix inlineResolver adding schema type. (#730)
- Fixing relative references Supporting
./(#726) (#752) - Resolve RequestBody Reference (#747)
- Convert Server with relative location to absolute url (#773)
- Numerous 2.0 -> 3.0 conversion fixes (#732) (#740) (#756) (#758) (#762) (#765) (#777) (#785)
(#786) (#790) (#794)
Known Issues
- Not resolving relative ref in classpath (WIP #700)
Swagger-parser 1.0.37 released!
Swagger-parser 2.0.1 released!
Minor bug fix release:
Parser
Converter
- Fix missing SwaggerParseResult.message in Converter (#716)
- Handle minLength, maxLength and pattern (#714)
- Fix oas2 parameter conversion (#711)
- Missing properties body parameter conversion parser (#688)
Known Issues
- Not resolving relative ref in classpath
- Not resolving relative ref without
./
Swagger-parser 1.0.36 released!
Swagger-parser 2.0.0 released!
The Swagger team is proud to announce the GA Release of the swagger-parser library.
In order to better improve these libraries and tools, we ask that you start using them and provide us with feedback in form of issues on the github repository. The issues are a huge help in finding what’s missing or not working properly (though note some issues are already submitted). We would also appreciate any PRs that improve existing or new tickets.
Notable Changes:
- Fix/multiple composed model (#635)
- Avoid overflow when storing an int64 in an Integer #636
- Fix for issue #647: update ref in requestBodies (#648)
- Remove allEmptyValue from body param and headers (#653)
- Add logging to parser(#660)
- Fix for issue #676: convert integer elements of enum into the correct type (#677)
- Numerous 2.0 -> 3.0 conversion fixes (#662) (#661)
Known Issues:
- Not resolving relative ref in classpath
Swagger-parser 1.0.35 released!
Minor release fixing a couple of issues:
- Adding support to schema Property as Model in Response Object issue (#567)
- Fix to Relative Ref being treated as a URL (#658)
- Remove allEmptyValue from body param (#652)
- Avoid duplicating definitions when they have the same name (#646)
- Handle untyped schemas (#573)
- fix Parsing of Model "example" is not consistent with parsing of Property (#449)
Swagger-parser 2.0.0-rc3 released!
The Swagger team is proud to announce the rc3 release candidate of the swagger-parser library.
In order to better improve these libraries and tools, we ask that you start using them and provide us with feedback in form of issues on the github repository. The issues are a huge help in finding what’s missing or not working properly (though note some issues are already submitted). We would also appreciate any PRs that improve existing or new tickets.
Notable Changes:
- Support for additionalProperties Boolean and Schema (#612)
- Fix discriminator mapping If there are any name conflict for ComposedSchema (oneOf) #631
- Fixing ComposedSchema resolving relative refs issues (#626) (#630)
- Fix trace method parsing (#625)
- Fix in:cookie in apiKey security schemes (#624)
- Fixing parsing of security Requirements (#615)
- Fixing additionalProperties resolving remote refs (#605)
- Numerous 2.0 -> 3.0 conversion fixes