2016-10-26 06:48:03 +00:00
# Release Checklist
2019-12-21 01:17:39 +00:00
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.
2018-05-16 23:15:15 +00:00
2018-07-31 12:11:37 +00:00
- Update CHANGELOG.
2020-02-21 22:09:31 +00:00
- Verify that the compiled mitmweb assets are up-to-date.
2018-07-31 12:11:37 +00:00
- Verify that all CI tests pass.
2019-12-21 01:17:39 +00:00
- Verify that `mitmproxy/version.py` is correct. Remove `.dev` suffix if it exists.
2018-07-31 12:11:37 +00:00
- Tag the release and push to Github.
2018-06-16 11:36:39 +00:00
- `git tag v4.0.0`
2019-12-21 01:17:39 +00:00
- `git push origin v4.0.0`
2018-07-31 12:11:37 +00:00
- Wait for tag CI to complete.
2017-03-15 21:36:58 +00:00
2019-12-21 01:57:53 +00:00
### GitHub Releases
2018-05-17 09:25:32 +00:00
- Create release notice on Github
[here ](https://github.com/mitmproxy/mitmproxy/releases/new ) 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:
2018-07-31 12:11:37 +00:00
`You can find the latest release packages at https://mitmproxy.org/downloads/.`
2017-03-15 21:36:58 +00:00
2019-12-21 01:57:53 +00:00
### PyPi
2018-07-31 12:11:37 +00:00
- The created wheel is uploaded to PyPi automatically.
2019-12-21 01:57:53 +00:00
- Please verify that https://pypi.python.org/pypi/mitmproxy has the latest version.
2018-02-25 16:49:54 +00:00
2019-12-21 01:57:53 +00:00
### Homebrew
2018-05-17 09:25:32 +00:00
- The Homebrew maintainers are typically very fast and detect our new relese
within a day.
2018-05-17 08:47:21 +00:00
- 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>`
2017-03-15 21:36:58 +00:00
2019-12-21 01:57:53 +00:00
### Docker
2019-12-21 01:33:58 +00:00
- 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` .
2018-05-18 08:37:56 +00:00
2019-12-21 01:57:53 +00:00
### 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
2018-05-17 09:25:32 +00:00
- Update version here:
https://github.com/mitmproxy/www/blob/master/src/config.toml
2019-12-21 01:57:53 +00:00
- Update docs menu here:
https://github.com/mitmproxy/www/blob/master/src/themes/mitmproxy/layouts/partials/header.html
2018-07-31 12:11:37 +00:00
- Run `./build && ./upload-test` .
2019-12-21 01:57:53 +00:00
- If everything looks alright at https://www-test.mitmproxy.org, run `./upload-prod` .
2018-04-05 16:26:55 +00:00
2018-05-16 23:15:15 +00:00
2019-12-21 01:57:53 +00:00
### Prepare for next release
2019-12-21 01:17:39 +00:00
- Last but not least, bump the major version on master in
[https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/version.py ](mitmproxy/version.py ) and add a `.dev` suffix.
