[ANNOUNCEMENT] M1 Release Train - Swagger 2.0 Support

[Ron]

The Swagger team is proud to announce the M1 release of three of our main libraries and tools: swagger-js, swagger-ui and swagger-core. All release provide official initial support for Swagger 2.0’s main features. The missing features will be added in the next milestone releases 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 relevant 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.

These releases could not have happened without the intensive support of the Swagger community. Each of the projects had a few PRs that really helped us push these projects forward!

Be aware that the release notes contain the notable changes, but there may some changes that we missed in the list.

Swagger-JS - 2.1.1-M1

Notable Features:

• First official milestone release of Swagger 2.0 support. Backwards compatible with Swagger 1.2.
• Unified API to initialize either 1.1, 1.2, 2.0 clients.
• Replace cake with gulp as the build tool.
• Rebuild the test framework with mocha and pure javascript.
• Addressed syntax issues which were breaking older versions of Internet Explorer
• Allow for repeated models of the same type in sample objects.
• Provide a example value for ‘date’ format.
• Please note that 2.1.1-M1 lives in Master

Notable Bug Fixes:

• Fixed query parameter encoding (#210)
• Fixed usage of content-type (#192)
• Fixed support for multi params with brackets (#191)
• Add array schema support (#147)
• Fix consumes/produces property propagation (#138)
• Added asCurl, mock modes for testing and debugging

Breaking Changes:

• The 1.x class, SwaggerApi, has been replaced with a unified SwaggerClient class.

Limitations:

• There are 2.0 features which are NOT implemented, as described in the https://github.com/swagger-api/swagger-js/milestones page

Swagger-UI - 2.1.1-M1

Notable Features:

• First official milestone release of Swagger 2.0 support. Backwards compatible with Swagger 1.2.
• Upgrade third library dependencies.
• Move to Gulp as the build tool.
• Swagger-UI can now load Swagger 2.0 specs if they are defined inline without loading from a remote server.
• Improved testing framework with selenium
• Improved possible security issues (such as XSS).
• Added support for GFM where applicable for Swagger 2.0 specs.
• Modified the responses section to accommodate Swagger 2.0 changes.
• New OAuth2 Access Code flow support.
• Hovering over properties now shows the validation constraints.
• Please note that 2.1.1-M1 lives in Master

Notable Bug Fixes:

• Issue with IE Compatibility view (#859)
• Issue with supportedSubmitMethods() returning null (#856)
• Issue with defaultValue not being filled (#855)
• Issue with deprecated operations (#852)
• Issue with formData parameters (#838)

Limitations:

• As with Swagger-js, please see the milestones page for unimplemented features (https://github.com/swagger-api/swagger-ui/milestones)

Swagger-Core - 1.5.0-M1

Notable Features:

• First official milestone release of Swagger 2.0 support. Swagger-Core now produces Swagger 2.0 specs only.
• (Software) API compatible with 1.3.6+.  For supported configurations, only a dependency upgrade is required. You may need a slight alteration to your configuration.
• Swagger-core is pure Java. Only the tests are in Scala, and those do not affect the dependencies of the library.
• Model introspection is now done by Jackson, and is much more robust.
• No more reliance on com.sun.* packages, making swagger-core safe for Google App Engine deployments.
• New, extension model for processing different annotation types.  Extensions are loaded via Java SPI, see https://github.com/swagger-api/swagger-core/blob/develop_2.0/modules/swagger-jaxrs/src/main/java/com/wordnik/swagger/jaxrs/ext/SwaggerExtension.java
• Available on Maven central, and the sources are in the 1.5.0-M1 branch. PRs should be submitted against the develop_2.0 branch.
• Please note that the swagger-core-1.5.x-M1 code lives in the 1.5.0-M1 branch.

Limitations:

• There will be a M2 and M3 release of swagger-core which will provide updated support for Play! framework and scala-based servers
• Subresource support is not implemented
• Model converters have a new, incompatible signature with 1.3.x.  Please see https://github.com/swagger-api/swagger-core/blob/develop_2.0/modules/swagger-core/src/main/java/com/wordnik/swagger/converter/ModelConverter.java for details of the new interface