Release Checklist

Check if mitmproxy-rs needs a new release.
Make sure that CHANGELOG.md is up-to-date with all entries in the "Unreleased" section.
Invoke the release workflow from the GitHub UI.
The spawned workflow runs will require manual confirmation on GitHub which you need to approve twice: https://github.com/mitmproxy/mitmproxy/actions
Once everything has been deployed, update the website.
Verify that the front-page download links for all platforms are working.

CI will automatically push a wheel to GitHub:
https://pypi.python.org/pypi/mitmproxy

CI will automatically update the stable docs and create an archive version:
https://docs.mitmproxy.org/archive/vMAJOR/

CI will automatically push binaries to our download S3 bucket:
https://mitmproxy.org/downloads/

CI will automatically update the Microsoft Store version:
https://apps.microsoft.com/store/detail/mitmproxy/9NWNDLQMNZD7
There is a review process, binaries may take a day to show up.

The Homebrew maintainers are typically very fast and detect our new relese within a day.
If you feel the need, you can run this from a macOS machine: brew bump-cask-pr mitmproxy

The website does not need to be updated for patch releases. New versions are automatically picked up once they are on the download server.
Update version here: https://github.com/mitmproxy/www/blob/main/src/config.toml
Update docs menu here: https://github.com/mitmproxy/www/blob/main/src/themes/mitmproxy/layouts/partials/header.html
Run ./build && ./upload-test.
If everything looks alright at https://www-test.mitmproxy.org, run ./upload-prod.

Last but not least, bump the major version on main in https://github.com/mitmproxy/mitmproxy/blob/main/mitmproxy/version.py and add a .dev suffix.