forked from https://github.com/mitmproxy/mitmproxy/ (bubble branch has our minor changes) https://github.com/mitmproxy/mitmproxy/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Maximilian Hils 56e108bcfc pyinstaller: add publicsuffix2 hook 4 years ago
..
docker Merge pull request #3329 from Kriechi/readme-slogan 4 years ago
hooks pyinstaller: add publicsuffix2 hook 4 years ago
installbuilder Such CI, Very Wow. (#3182) 5 years ago
specs fix pyinstaller 7 years ago
windows-store-experiment minor fixes for windows package 6 years ago
.gitignore pin snapshot server hostkey, update pysftp 6 years ago
README.md docker: auto-update latest tag 4 years ago
__init__.py cibuild: Consolidate build environment and add tests 5 years ago
cibuild.py docker: auto-update latest tag 4 years ago

README.md

Release Checklist

These steps assume you are on the correct branch and have a git remote called origin that points to the mitmproxy/mitmproxy repo. If necessary, create a major version branch starting off the release tag (e.g. git checkout -b v4.x v4.0.0) first.

  • Update CHANGELOG.
  • Verify that all CI tests pass.
  • Verify that mitmproxy/version.py is correct. Remove .dev suffix if it exists.
  • Tag the release and push to Github.
    • git tag v4.0.0
    • git push origin v4.0.0
  • Wait for tag CI to complete.

GitHub Releases

  • Create release notice on Github here if not already auto-created by the tag.
  • We DO NOT upload release artifacts to GitHub anymore. Simply add the following snippet to the notice: You can find the latest release packages at https://mitmproxy.org/downloads/.

PyPi

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-formula-pr --url https://github.com/mitmproxy/mitmproxy/archive/v<version number here>

Docker

  • The docker image is built by our CI workers and pushed to Docker Hub automatically.
  • Please verify that https://hub.docker.com/r/mitmproxy/mitmproxy/tags/ has the latest version.
  • The latest and latest-ARMv7 tags should auto-update. @mhils introduced this after the 5.0.0 release. Please verify that this is the case and remove this notice. For reference, this is how to do it manually: export VERSION=4.0.3 && docker pull mitmproxy/mitmproxy:$VERSION && docker tag mitmproxy/mitmproxy:$VERSION mitmproxy/mitmproxy:latest && docker push mitmproxy/mitmproxy:latest.

Docs

  • ./build-current. If everything looks alright, continue with
  • ./upload-stable,
  • ./build-archive, and
  • ./upload-archive v4. Doing this now already saves you from switching back to an old state on the next release.

Website

Prepare for next release