Grasscutters/mitmproxy
3
0
Fork 0
mirror of https://github.com/Grasscutters/mitmproxy.git synced 2024-11-25 18:03:50 +00:00
Code Issues Projects Releases Wiki Activity
ca91780ff4
mitmproxy/release
History
Maximilian Hils f6f9944160 pyinstaller: add passlib hook
2017-09-04 18:07:27 +02:00
..
hooks pyinstaller: add passlib hook 2017-09-04 18:07:27 +02:00
installbuilder InstallBuilder (#1826) 2016-12-11 23:07:47 +01: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
.gitignore move bin into release, update rtool 2016-02-18 11:25:29 +01:00
README.md fix markdown 2017-04-30 11:21:28 +02:00
rtool.pem add release 2016-02-15 14:58:53 +01:00
rtool.py improve version specifiers 2017-01-23 20:33:12 +01:00
setup.py bump rtool dependencies 2017-08-18 09:57:08 +02:00

README.md

Release Checklist

Make sure run all these steps on the correct branch you want to create a new release for!

  • Verify mitmproxy/version.py
  • Update CHANGELOG
  • Verify that all CI tests pass
  • Tag the release and push to Github
  • Wait for tag CI to complete

GitHub Release

PyPi

  • Upload wheel to pypi: twine upload <mitmproxy-...-.whl

Docker

  • Update docker-releases repo
    • Create a new branch based of master for major versions.
    • Update the dependencies in alpine/requirements.txt
      • Creating a fresh venv, pip-installing the new wheel in there, and then export all packages:
      • virtualenv -ppython3.5 venv && source venv/bin/activate && pip install mitmproxy && pip freeze
    • Tag the commit with the correct version
      • 2.0.0 for new major versions
      • 2.0.2 for new patch versions
      • 2.0 always points to the latest patch version of the 2.0.x series (update tag + force push)
  • Update latest tag here

After everything is done, you might want to bump the version on master in https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/version.py if you just created a major release.