NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
Sphinx plugin which renders a OpenAPI specification with Swagger
Last release 10 days ago
24 Sep 2026
Ships fairly regularly
a new release about every 3 months
Nearly every release is documented
notes for 30 of 30 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
30 releases · first in 2022
One column per quarter.
Removed support for python 3.10
The spec copied into _static is now overwritten on every build, instead of keeping the content of the first build
_static is now overwritten on every build, instead of keeping the content of the first build (#625)Fixed an issue causing an ImportError on python 3.10
ImportError on python 3.10The OpenAPI spec is now indexed for the sphinx search
Add ability to mirror Swagger resources to doctree
### Removals - Removed support for sphinx 7.x ### Changes - Updated the release actions
* Add support for sphinx 9
* Removed support for sphinx 6.x * Removed support for python 3.9
* Add support for python 3.14
Pass the Swagger UI options also for inline rendering.
Added missing dependency on typing-extensions
typing-extensionsFixed a bug related to referencing a specification from a parent directory of the Sphinx source directory, such as when documentation is co-located wi
Fixed a bug related to referencing a specification from a parent directory of the Sphinx source directory, such as when documentation is co-located with source code.
Before this fix, when a specification was several subdirectories from the documentation, the specification could be copied to a parent directory of the build HTML output and prevent the display of the specification.
With this fix, deeply nested specifications (../../../../openapi.yaml)
have the .. values that are parents of the Sphinx source directory
replaced with the text dot-dot. This fix ensures that deeply
nested specifications are copied to a subdirectory of the _static
directory in the HTML output.
Refactored copying the specification to the HTML output and referencing the path to the specification in the HTML page.
docs/api/foo/openapi.yaml
and docs/api/bar/openapi.yaml so that different files can use
the same file name.Fixed an issue causing a spec to be linked incorrectly when the dirhtml builder is used.
dirhtml builder is used.Fixed an issue causing a spec to be linked incorrectly when the source document is in a subfolder but the referenced spec is in another one
Fix some errors when the spec is in a subdirectory
This release combines the previous three way into one directive streamlining the project
This release combines the previous three way into one directive streamlining the project
swagger configuration from conf.py (however, the swagger_* configuration remain).
Use the swagger-plugin directive with the full-page option to active the sameinline-swagger directive.
Use the swagger-plugin directive insteadAdd a swagger-plugin directive:
Add a swagger-plugin directive:
<head> element of the HTML page.swagger configuration in the conf.py file.* Add support for python 3.13 * Drop support for python 3.8
* Add support for sphinx 8
No new features but a switch of the way this package is released
Official support file paths for swagger_present_uri, swagger_bundle_uri and swagger_css_uri
swagger_present_uri, swagger_bundle_uri and swagger_css_uriswagger_present_uri, swagger_bundle_uri and swagger_css_uri* Support python 3.12
Support for inline swagger pages
* Support Sphinx 7
Make swagger_plugin_for_sphinx.plugin private
swagger_plugin_for_sphinx.plugin privateswagger_plugin_for_sphinx.__version__swagger_plugin_for_sphinx.plugin use swagger_plugin_for_sphinxAdd official support for python 3.11
* Require at least python 3.7.2 * Support sphinx 5.x
internal change from os.path to pathlib
os.path to pathlibInitial release
Initial release
Your coding agent can read these notes before it upgrades. Set up the MCP server →