Creating a release

Make sure that git-cliff is installed and arch-update is up to date on your system.
Export a TAG variable containing the new tag for the release:

export TAG="X.Y.Z"

Bump version in where necessary:

sed -i "s/$(arch-update -V | cut -f2 -d " ")/${TAG}/g" doc/man/arch-update.* doc/man/fr/arch-update.* po/* src/script/arch-update.sh

Update changelog:

git-cliff -up CHANGELOG.md
sed -i "s|\[unreleased\]|\[v${TAG}\](https://github.com/Antiz96/arch-update/releases/tag/v${TAG})\ -\ $(date '+%Y-%m-%d')|g" CHANGELOG.md

Commit, sign and push changes directly to the main branch (we want the tagged commit to be signed with the OpenPGP Key listed in MAINTAINERS.md and not with the GitHub signature key automatically used when merging a pull request; this implies temporarily allowing administrators to bypass branch protections rules):

git add .
git commit -SD33FAA16B937F3B2 -m "chore(release): v${TAG}"
git push

Create, sign and push the new tag:

git tag v${TAG} -u D33FAA16B937F3B2 -m "v${TAG}"
git push origin v${TAG}

Create a release on GitHub, copy/paste release notes from the changelog and sign the auto-generated source tarball:

cd ~/Downloads
curl https://github.com/Antiz96/arch-update/archive/refs/tags/v${TAG}.tar.gz -o arch-update-${TAG}.tar.gz
gpg --local-user D33FAA16B937F3B2 --armor --detach-sign arch-update-${TAG}.tar.gz
sha256sum arch-update-${TAG}.tar.gz > arch-update-${TAG}.tar.gz.sha256
gpg --local-user D33FAA16B937F3B2 --armor --detach-sign arch-update-${TAG}.tar.gz.sha256
rm -f arch-update-${TAG}.tar.gz

Upload the 3 produced files as assets in the release, re-enable the branch protection rules on the main branch for administrators and unset the TAG variable:

unset TAG