Maximilian Hils 56e108bcfc | 4 years ago | |
---|---|---|
.. | ||
docker | 4 years ago | |
hooks | 4 years ago | |
installbuilder | 5 years ago | |
specs | 7 years ago | |
windows-store-experiment | 6 years ago | |
.gitignore | 6 years ago | |
README.md | 4 years ago | |
__init__.py | 5 years ago | |
cibuild.py | 4 years ago |
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.
mitmproxy/version.py
is correct. Remove .dev
suffix if it exists.git tag v4.0.0
git push origin v4.0.0
You can find the latest release packages at https://mitmproxy.org/downloads/.
brew bump-formula-pr --url https://github.com/mitmproxy/mitmproxy/archive/v<version number here>
export VERSION=4.0.3 && docker pull mitmproxy/mitmproxy:$VERSION && docker tag mitmproxy/mitmproxy:$VERSION mitmproxy/mitmproxy:latest && docker push mitmproxy/mitmproxy:latest
../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../build && ./upload-test
../upload-prod
..dev
suffix.