v0.31.2

docs/API_ACCESS.md

@@ -132,7 +132,7 @@ promise to erase browser/OS screenshots or data intentionally downloaded by an a
 ## First build / offline assets (fixed in 0.7.2)
 
 No `SWAGGER_UI_DOWNLOAD_URL` environment variable or `.cargo/config.toml` is required.
-The default is Swagger UI **5.32.11**, selected by `scripts/build/swagger_assets.py` and
+The default is Swagger UI **5.33.1**, selected by `scripts/build/swagger_assets.py` and
 called from this application's `build.rs`. The former `utoipa-swagger-ui` adapter
 is removed: there is no separate dependency build silently choosing its older
 historical browser default. Direct Cargo builds using `--manifest-path` use the
@@ -160,10 +160,10 @@ release binaries**, served behind the existing admin guard. No runtime download,
 CDN, public asset endpoint or alternate authentication mechanism was introduced.
 
 An offline or GitHub-restricted build can use a reviewed local copy of the same
-GitHub **tag archive**, with its original `swagger-ui-5.32.11/` directory structure:
+GitHub **tag archive**, with its original `swagger-ui-5.33.1/` directory structure:
 
 ```bash
-export SWAGGER_UI_DOWNLOAD_URL=file:///srv/build-assets/swagger-ui-5.32.11.zip
+export SWAGGER_UI_DOWNLOAD_URL=file:///srv/build-assets/swagger-ui-5.33.1.zip
 # Optional: require the archive digest independently verified by your build team.
 # export SWAGGER_UI_ARCHIVE_SHA256=<64-hex-digit-verified-digest>
 bash dev.sh check
@@ -237,4 +237,4 @@ unchanged. No configuration schema migration is needed for existing header rules
 - Swagger UI configuration: https://swagger.io/docs/open-source-tools/swagger-ui/usage/configuration/
 - Cargo configuration discovery: https://doc.rust-lang.org/cargo/reference/config.html
 - Cargo build scripts: https://doc.rust-lang.org/cargo/reference/build-scripts.html
-- Pinned browser release: https://github.com/swagger-api/swagger-ui/tree/v5.32.11
+- Pinned browser release: https://github.com/swagger-api/swagger-ui/tree/v5.33.1