HTTPie release process

Welcome on the documentation part of the HTTPie release process.

If you do not know HTTPie, have a look here.
If you are looking for HTTPie installation or upgrade instructions, then you can find all you need for your OS on that page. In the case you do not find your OS, let us know.
If you are looking for technical information about the HTTPie packaging, then you are at the good place.

About

You are looking at the HTTPie packaging documentation, where you will find valuable information about how we manage to release HTTPie to lots of OSes, including technical data that may be worth reading if you are a package maintainer.

The overall release process starts simple:

Bump the version identifiers in the following places:
- httpie/__init__.py
- docs/packaging/windows-chocolatey/httpie.nuspec
- CHANGELOG.md
Commit your changes and make a PR against the master.
Merge the PR, and tag the last commit with your version identifier.
Make a GitHub release (by copying the text in CHANGELOG.md)
Push that release to PyPI (dispatch the Release PyPI GitHub action).
Once PyPI is ready, push the release to the Snap, Homebrew and Chocolatey with their respective actions.
Go to the httpie/debian.httpie.io repo and trigger the package index workflow.

Company-specific tasks

Blank the master_and_released_docs_differ_after value in config.json.
Update the contributors list.
Update the HTTPie version bundled into Termible (example).

Finally, spread dowstream

Find out how we do release new versions for each and every supported OS in the following table. A more complete state of deployment can be found on repology, including unofficial packages.

OS	Maintainer
Arch Linux, and derived	trusted person
CentOS, RHEL, and derived	trusted person
Fedora	trusted person
Debian, Ubuntu, and derived	HTTPie
Homebrew, Linuxbrew	HTTPie
Snapcraft	HTTPie
Windows — Chocolatey	HTTPie

:new: You do not find your system or you would like to see HTTPie supported on another OS? Then let us know.