Release Procedure

Pre-release work

• Check that you've included the latest CLI output in the documentation homepage
• Update the CHANGELOG.md

Release

Push new docs

mkdocs gh-deploy

Commit and push release commit to github

Template commit message:

0.1.0 release

[copy release notes here]

Full Release details in CHANGELOG.md.

WAIT FOR CI TO FINISH TESTING

Tag git commit

export GITLINT_VERSION_TAG=v$(hatch version); echo $GITLINT_VERSION_TAG
git tag $GITLINT_VERSION_TAG
git tag --list
git push --tags

Create a new release on github

Go to the releases page and create a new release. Copy in changes from the raw CHANGELOG.md

Post Release Steps

Bump version to dev

Bump the version number in gitlint/__init__.py

# From host system
export NEW_VERSION="0.9.0dev"
echo -e "Version bump to $NEW_VERSION\n\nBumped version to $NEW_VERSION." > /tmp/gitlint-$NEW_VERSION-version-bump-commitmsg
git commit -F /tmp/gitlint-$NEW_VERSION-version-bump-commitmsg
git tag $NEW_VERSION
git tag --list
git show # Tag should show up
git push

Make sure to shutdown any AWS Windows testing VMs

Ask harens in associated Release Plan issue to push builds for homebrew and macports

Create Release Plan issue and milestone for next release on github