aboutsummaryrefslogtreecommitdiffstats
path: root/release/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'release/README.md')
-rw-r--r--release/README.md14
1 files changed, 6 insertions, 8 deletions
diff --git a/release/README.md b/release/README.md
index 8632d644..fb245e23 100644
--- a/release/README.md
+++ b/release/README.md
@@ -27,20 +27,18 @@ These steps assume you are on the correct branch and have a git remote called `o
- 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>`
+ `brew bump-formula-pr --url https://github.com/mitmproxy/mitmproxy/archive/v<version number here>.tar.gz mitmproxy`
### 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`.
+- Please verify that the latest tag points to the most recent image (same digest / hash).
### 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.
+ - `./build.sh`. If everything looks alright, continue with
+ - `./upload-stable.sh`,
+ - `DOCS_ARCHIVE=true ./build.sh`, and
+ - `./upload-archive.sh v4`. Doing this now already saves you from switching back to an old state on the next release.
### Website
- Update version here: