Grasscutters/mitmproxy
3
0
Fork 0
mirror of https://github.com/Grasscutters/mitmproxy.git synced 2024-11-22 15:37:45 +00:00
Code Issues Projects Releases Wiki Activity
e0b8a48392
mitmproxy/release
History
Maximilian Hils 34a620e57b
Docker: Add aarch64 Images (#4637) 
* feat(cibuild): add buildx multi arch builds

* chore: add changelog for arm64

* temporarily enable docker ci job for PRs

* Update cibuild.py

* Update cibuild.py

* chore(cibuild): create docker-container xbuilder

* chore(cibuild): fix lint

* temporarily remove run check to see error message

* Update cibuild.py

* Update cibuild.py

* Update cibuild.py

* Update main.yml

* Update main.yml

* Update main.yml

* Update cibuild.py

* Update cibuild.py

* Update Dockerfile

* cleanup #1

* next test

* move to test branch

* fixup

* now upload

* enable armv6/7

* use multi-stage build to reduce image size

* armv7?

* drop armv6/armv7

Co-authored-by: Niels Hofmans <hello@ironpeak.be>
2021-06-15 13:47:50 +00:00
..
docker Docker: Add aarch64 Images (#4637) 2021-06-15 13:47:50 +00:00
hooks remove upstreamed pyinstaller hooks 2020-11-02 02:39:56 +01:00
installbuilder Windows: build pyinstaller onedir and use it for installer 2021-01-05 15:56:33 +01:00
specs Windows: build pyinstaller onedir and use it for installer 2021-01-05 15:56:33 +01:00
windows-store-experiment Improve Markdown syntax(styling) (#4496) 2021-03-11 19:13:02 +01:00
__init__.py cibuild: Consolidate build environment and add tests 2018-05-24 11:06:43 +12:00
.gitignore
cibuild.py Docker: Add aarch64 Images (#4637) 2021-06-15 13:47:50 +00:00
deploy.py Harden CI Pipeline (#4590) 2021-05-11 11:17:09 +02:00
README.md Fix typo: Github should be GitHub (#4541) 2021-04-05 10:08:21 +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 v4.0.0) first.

  • Update CHANGELOG.
  • Verify that the compiled mitmweb assets are up-to-date.
  • 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 v4.0.0
    • git push origin v4.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.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

Prepare for next release