diff options
| author | Maximilian Hils <git@maximilianhils.com> | 2017-04-28 14:43:49 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-28 14:43:49 +0200 |
| commit | b537997f4f5d7c33562414a414913b6cd89f99c3 (patch) | |
| tree | d08b472bd8a44cfe888a9c70383a10caab7cfa26 /release | |
| parent | 05e1f221438c4d1fe63ae9c39dc18ee12e0bcdf5 (diff) | |
| download | mitmproxy-b537997f4f5d7c33562414a414913b6cd89f99c3.tar.gz mitmproxy-b537997f4f5d7c33562414a414913b6cd89f99c3.tar.bz2 mitmproxy-b537997f4f5d7c33562414a414913b6cd89f99c3.zip | |
Update README.md
Diffstat (limited to 'release')
| -rw-r--r-- | release/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/release/README.md b/release/README.md index c48a4e2b..74acc571 100644 --- a/release/README.md +++ b/release/README.md @@ -20,6 +20,6 @@ Make sure run all these steps on the correct branch you want to create a new rel - Update the dependencies in [alpine/requirements.txt](https://github.com/mitmproxy/docker-releases/commit/3d6a9989fde068ad0aea257823ac3d7986ff1613#diff-9b7e0eea8ae74688b1ac13ea080549ba) * 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` -- Update `latest` tag [https://hub.docker.com/r/mitmproxy/mitmproxy/~/settings/automated-builds/](here) +- Update `latest` tag [here](https://hub.docker.com/r/mitmproxy/mitmproxy/~/settings/automated-builds/) After everything is done, you might want to bump the version on master in [https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/version.py](mitmproxy/version.py) if you just created a major release. |