Releases: swagger-api/swagger-parser
Swagger-parser 2.0.0-rc0 released!
The Swagger team is proud to announce the rc0 release candidate of the swagger-praser library. This release candidate provides official initial support for OpenAPI 3.0’s main features. The missing features will be added in the next release candidates until the final release is available.
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 Features:
- First official release candidate of OpenAPI 3.0 support.
- Swagger-Parser will convert 2.0 to 3.0 upon loading.
- Available on Maven central, and the sources are in the 2.0 branch. PRs should be submitted against the 2.0 branch.
- Built with Java 8
We invite you to check the README for more information on how to use it.
Swagger-parser 1.0.32 released!
Minor update to update the swagger-core dependency which brings some vulnerability fixes in dependencies.
See https://github.com/swagger-api/swagger-core/releases/tag/v1.5.16 for more details.
Swagger-parser 1.0.31 released!
This minor fix has thrilling and tantalizing updates, namely:
- swagger-core updated to latest & greatest (1.5.15)
- security fix for possible BadPersonActivity(tm) in YAML #481
- Added missing descriptions for security definitions #482
Note: The security fix was generously found and fixed by @ mmosemmle by using the lgtm.com tool
Get it while it's hot!
swagger-parser 1.0.29 released!
It 'aint 3.0 support, but who cares! This is the latest update to the swagger-parser which adds the following:
Swagger-Parser 1.0.26 Released!
Some minor updates in the parser to support the swagger-core 1.5.12 release.
Improvements
- Better parsing of
BodyParameter
. Support extensions #360, #381 - Update HTTP client library to more secure version #397
- Show SSL errors more gracefully #383
Fixes
- No longer converting
minimum
,maximum
,default
values to double when parsing. Now usesBigDecimal
along with a string cache to keep the original formatting without interpolation #400
Swagger-parser 1.0.25 Released!
Well what do you know, a late holiday gift! Here's a new release of swagger-parser
to bring you into the New Year the right way.
Enhancements
- Updated to Jackson 2.8.4, along with the latest swagger-core
- Parsing of non-string
enum
values #363 - URL cleaning to support 1.1, 1.2 specs #367
- Parsing of
uniqueItems
,multipleOf
#372 - Less printlns #370
Fixes
allOf
with single element no longer gives error #371
Swagger-parser 1.0.23 Released
So many updates! 1.0.23 brings a ton of fixes and enhancements when dealing with everyone's favorite dinner-time topic: JSON References. Yes now, we are correctly traversing from host-to-host, from relative-to-absolute, etc. It's a blast to follow along with the tests, so check them out! (Note there is very little difference between a bug fix and enhancement, so consider the selection between the two to be pretty much random)
Bug Fixes:
- Fixed NPE when parsing shared path parameters #268
- Nested references are now correctly resolved #270
- No more duplication of path parameters #271
- Incorrect vendor extensions in remote references #274
- Now correctly resolving nested references in arrays #286
- Correct escaping of JSON Pointers #289
- Collection type format parsing was incorrect #291, #292
Enhancements:
- Better detection of content type--no longer using extensions #276
- Resolution of recursive references #278
- Resolving direct model references now supported #297
- Resolution of external files in folders now supported #299, #304, #306, #312, #314
- Resolution of remote -> relative references across hosts is now supported #316, #319, #325, #330
Swagger-parser 1.0.16 Released!
Fixed a small glitch where type checking may not behave as expected #159
Swagger-parser 1.0.15 Released!
Swagger-parser 1.0.13 Released!
This itty-bitty release provides proper feedback when an invalid (i.e. unparseable) swagger is specified. Required for the swagger-inflector release!