Updates

anonymizer updates itself via a clear in-UI flow. There’s no auto-update; you decide when.

How the update check works

1. Each time you launch the web UI, a background request fetches https://anonymizer.site/version.json with a 2-second timeout.
2. If a newer version is available, an [Update] banner appears at the top of the UI. Clicking it shows the changelog and an “Update now” button.
3. Clicking “Update now” launches a small detached process (anonymizer.updater) that runs uv tool upgrade docs-anonymizer and then prompts you to restart the web UI.

The check is the only outbound network request made by the product. The redaction engine itself never opens a socket — there’s a test that enforces this.

What’s in version.json

{
  "version": "0.1.0",
  "sha256": "abc123...",
  "url": "https://pypi.org/project/docs-anonymizer/0.1.0/",
  "released_at": "2026-08-01T12:00:00Z"
}

The sha256 matches the wheel published on PyPI for that version, so you can verify integrity before applying.

Disabling the check

For air-gapped or paranoid setups:

export ANONYMIZER_DISABLE_UPDATE_CHECK=1
anonymize

This skips the version fetch entirely. The banner never appears.

Update from a private mirror

If your organization mirrors PyPI internally, set UV_INDEX_URL before launching the updater:

export UV_INDEX_URL=https://pypi.your-corp.example/simple

The detached updater inherits the environment, so uv tool upgrade pulls from your mirror.

See Corporate setup for the full IT-admin scenario.