Py-swagger-ui

No source changes.

This release moves Swagger UI to [`swagger-client3.9.0`](https://github.com/swagger-api/swagger-js/releases/tag/v3.9.0).

Changelog

* improvement: OAS3 $ref friendly-name regex in model.jsx (via 5334)
* improvement: add `isShown` check to <ModelCollapse />'s prop `expanded` logic (via 5331)
* improvement: relax schema description styling so Markdown can be effective (via 5340)
* security: CVE-2018-20834 (non-user-facing, via 5368)

swagger-ui-react3.22.0` lacked the changes that were advertised for it in that version - specifically, `docExpansion` support was missing.

`swagger-ui-react3.22.1` is now available with the new changes. See 5294 for more information.

Changelog

* improvement: error message when rendering XML example (via 5253)
* fix: refuse to render non-string Markdown field values (via 5295)

This release introduces a new configuration option (`withCredentials`) which allows control of Swagger UI's underlying Fetch/XHR instance's [credential inclusion mode](https://fetch.spec.whatwg.org/#ref-for-credentials③). You may find this option helpful if your API requires an authentication/authorization scheme that Swagger UI doesn't directly support, but can be handled out-of-band by your browser.

Also notable: GitHub Flavored Markdown table syntax is now supported in our OpenAPI 3 Markdown parser, `swagger-ui-react`'s underlying UI system object is now exposed in the `onComplete` prop callback, `react-addons-perf` is removed from our dependencies to avoid BSD+Patents licensing, and we've improved how Markdown is rendered across Swagger UI.

Changelog

* feature: add `withCredentials` configuration key (via 5149)
* improvement: expose system object in swagger-ui-react's onComplete callback (via 5221)
* improvement: support GFM table syntax in OpenAPI 3.0 (via 5224)
* improvement: expose docExpansion as a prop in swagger-ui-react (via 5242)
* fix: Markdown styling nits and inconsistencies (via 5235)
* fix: generate gzipped Docker assets at runtime (via 5219)
* housekeeping: bump minimum Cypress version (via 5233)
* housekeeping: remove react-addons-perf dependency (via 5229)
* housekeeping: fix typo in README (via 5246)

This release marks the introduction of a new flavor of Swagger UI: [`swagger-ui-react`](https://www.npmjs.com/package/swagger-ui-react).

This new module exports a component for use in React applications, and allows you to use any React version you'd like, without fear of colliding with Swagger UI's internal React version.

We recommend that anyone using Swagger UI within a React application migrate to this module, instead of continuing to mount Swagger UI onto a React-created DOM node by ID.

This release also includes some fixes that improve Swagger UI's handling of rare edge cases in the resolver engine.

_Note: this release was also erroneously pushed out as `v3.20.10` - both versions' contents are identical._

Changelog

* feature: `swagger-ui-react` module (via 5207)
* improvement(docker): gzip static files (via 5199)
* improvement: gracefully render malformed and empty requestBodies (via 5208)
* improvement: subtree resolver batch handling (via 5193)

**This release contains a security fix that addresses a cross-site scripting vulnerability.** If you use Swagger UI to display untrusted OpenAPI documents, you should upgrade to this version ASAP.

This release also changes Swagger UI's `OperationSummary` component to better tolerate badly-formed (i.e., non-string) `summary` fields.

**Changelog**:
* fix: gracefully handle non-string operation summaries (via 5189, 5191)
* fix: sanitize URLs used for OAuth auth flow (via 5190)