vee1e/mitmproxy
1
0
Fork 0
mirror of https://github.com/vee1e/mitmproxy.git synced 2026-09-02 10:47:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
mitmproxy/release
History
Manuel Meitinger e11626395e
Fix running hook issue and signal proxyserver updates. (#5512) 
* add startup hook

* remove StartupHook

* add instance state reports

* make server stop log entries clearer

* fix default param issue

* add SyncSignal and AsyncSignal

* fix signal issues

* simpler update handling

* fix coverage

* minor change to better reflect server update state

* fix reuse tests on linux/wsl

* exterminate `mitmproxy.exceptions.TypeError`

Co-authored-by: Maximilian Hils <git@maximilianhils.com>
2022-08-14 00:11:01 +02:00
..
docker
installbuilder
specs simplify ci build script, add MSIX installer and Microsoft store. 2022-07-25 01:22:57 +02:00
windows-installer revise display names 2022-07-25 14:38:21 +02:00
.gitignore
build-and-deploy-docker.py simplify ci build script, add MSIX installer and Microsoft store. 2022-07-25 01:22:57 +02:00
build.py Fix running hook issue and signal proxyserver updates. (#5512) 2022-08-14 00:11:01 +02:00
deploy-microsoft-store.py simplify ci build script, add MSIX installer and Microsoft store. 2022-07-25 01:22:57 +02:00
deploy.py ci: don't build installers for PRs 2022-07-29 13:42:42 +02:00
README.md simplify ci build script, add MSIX installer and Microsoft store. 2022-07-25 01:22:57 +02:00

README.md

Release Checklist

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 4.0.0) first.

  • Update CHANGELOG.
  • Verify that the compiled mitmweb assets are up-to-date (npm start prod).
  • Verify that all CI tests pass.
  • Verify that mitmproxy/version.py is correct. Remove .dev suffix if it exists.
  • Tag the release and push to GitHub.
    • git tag 4.0.0
    • git push origin 4.0.0
  • Wait for tag CI to complete.

GitHub Releases

  • Create release notice on GitHub here 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: You can find the latest release packages at https://mitmproxy.org/downloads/.

PyPi

Homebrew

  • 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>.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.
  • Please verify that the latest tag points to the most recent image (same digest / hash).

Docs

  • ./build.py. If everything looks alright, continue with
  • ./upload-stable.sh,
  • DOCS_ARCHIVE=true ./build.py, and
  • ./upload-archive.sh v4. Doing this now already saves you from switching back to an old state on the next release.

Website

Prepare for next release