aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Kriechbaumer <thomas@kriechbaumer.name>2020-04-13 10:17:08 +0200
committerThomas Kriechbaumer <thomas@kriechbaumer.name>2020-04-13 10:17:08 +0200
commit6d6876470744eeb844726dcfd36b77d7aef2e60a (patch)
tree2d57158d732dad58e74c5936570cd3afb6632cc7
parent16c98765fc07aa911148317dbc97186d32c18828 (diff)
downloadmitmproxy-6d6876470744eeb844726dcfd36b77d7aef2e60a.tar.gz
mitmproxy-6d6876470744eeb844726dcfd36b77d7aef2e60a.tar.bz2
mitmproxy-6d6876470744eeb844726dcfd36b77d7aef2e60a.zip
remove outdated release intructions
-rw-r--r--release/README.md4
1 files changed, 1 insertions, 3 deletions
diff --git a/release/README.md b/release/README.md
index 0a51d125..fb245e23 100644
--- a/release/README.md
+++ b/release/README.md
@@ -32,9 +32,7 @@ These steps assume you are on the correct branch and have a git remote called `o
### 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 tag 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.sh`. If everything looks alright, continue with