mitmproxy/release
Maximilian Hils 886055df17
Update to Python 3.14 (#7918)
* update to Python 3.14

* [autofix.ci] apply automated fixes

* fix python 3.14 compatibility

* bump minimum required zstandard version

0.15 was causing CI issues with Python 3.14.

* Revert "Bump hypothesis dependency (#7865)"

This reverts commit 0981668515.

windows-curses has no abi3 wheels, which blocks adoption of Python 3.14. Kill it with fire.

* remove compression from HAR tests

* add `build-essential` to build jobs

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2025-10-15 21:32:53 +02:00
..
docker Update to Python 3.14 (#7918) 2025-10-15 21:32:53 +02:00
installbuilder
specs
windows-installer
.gitignore
build.py switch to uv (#7662) 2025-04-16 18:38:35 +02:00
deploy-microsoft-store.py clarify MSFT env vars 2025-08-24 22:00:37 +02:00
deploy.py
github-release-notes.txt
README.md
release.py Run pyupgrade and improve f-strings (#7837) 2025-08-19 20:15:46 +02:00
selftest.py

Release Checklist

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

GitHub Releases

PyPi

Docker

Docs

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

Download Server

Microsoft Store

Homebrew

  • 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

Website

Prepare for next release