mitmproxy/release
2019-12-21 02:57:53 +01:00
..
docker Merge pull request #3329 from Kriechi/readme-slogan 2019-09-28 16:45:00 +02:00
hooks fix appveyor build script 2017-12-30 18:48:49 +01:00
installbuilder Such CI, Very Wow. (#3182) 2018-06-02 21:37:44 +02:00
specs fix pyinstaller 2016-11-28 00:51:52 +01:00
windows-store-experiment minor fixes for windows package 2017-06-14 14:35:51 +02:00
__init__.py cibuild: Consolidate build environment and add tests 2018-05-24 11:06:43 +12:00
.gitignore pin snapshot server hostkey, update pysftp 2018-01-04 14:12:30 +01:00
cibuild.py Use Github Actions for CI (#3713) 2019-11-19 18:15:08 +01:00
README.md update release instructions 2019-12-21 02:57:53 +01:00

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 on Travis and pushed to Docker Hub automatically.
  • Please check https://hub.docker.com/r/mitmproxy/mitmproxy/tags/ about the latest version.
  • Update latest tag: 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