Releasing
This page describes the steps for publishing a new Home Assistant release. Those steps requires that you don’t use forks but work with the repositories themself. The hass-release script is a helper to do a release.
Release preparation (3 days before release)
GitHub
- Merge
master
intodev
to make the PR mergeable. - Cut a release branch from
dev
. Example namerelease-0-57
. - Create a pull request from the release branch to
master
with the upcoming release number as the title. - Update
homeassistant/const.py
with the correct version number (remove thedev
tag) and push that commit to release branch.
Website
- Merge
current
intonext
- Cut release branch of
next
. For examplerelease-0-57
. - Open a PR from release branch to
current
with the upcoming release number as the title.
Release day
From creating the release branch till it has been merged, we tag bugfixes with the milestone for the release (create if doesn’t exist).
GitHub
- Cherry-pick the milestoned PRs that need to get into the release
python3 -m hassrelease milestone_cherry_pick 0.57
- Run
python3 -m hassrelease release_notes 0.56
for the release notes. - Once the release notes has been generated, issue
python3 -m hassrelease milestone_close 0.56
- Merge pull request (DO NOT SQUASH!). Use
Merge pull request
. - Go to releases, click
Draft a new release
and tag a new release on themaster
branch. “Tag version” and “Release title” are the version number (O.x
for major version,0.x.y
for minor and bug fix releases). Release description is the text from PR. Press “Publish release” to finish the process. - Merge
master
intodev
. - Update
homeassistant/const.py
with the upcoming version number (including thedev
tag) and push that commit to thedev
branch.
Website
- Create a blog post in the release branch and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in a message to documentation.
- Create missing documentation as stubs.
- Run
credits_generator
. - Update
_config.yml
with a link to the new release blog post and version number (at the bottom of the file). - Merge
current
into release branch ($ git checkout release-0-40 && git merge current
) to make the PR mergeable. - Merge pull request (blog post, updated frontpage, and all new documentation) to
current
. DO NOT SQUASH! - Merge
current
intonext
.
Docker Hub
Tags on Docker hub are automatically created when a release has been created on GitHub.
Python Package Index
Checkout the master
branch and run script/release
to publish the new release on Python Package Index.
Social media
- Use hootsuite to publish a link to the release post on social media.
Bugfix Release
- Checkout
master
and update it.git checkout master && git pull --rebase
- Create a new release branch from
master
.git checkout -b release-0-56-2
- Cherry-pick the PRs which were milestoned.
- Update
homeassistant/const.py
with the correct version number (incrementPATCH_VERSION
) and push that commit to release branch. - Create a pull request from the release branch to
master
with the upcoming release number as the title. - Merge pull request (DO NOT SQUASH!). Use
Merge pull request
. - Go to releases, click
Draft a new release
and tag a new release on themaster
branch. “Tag version” and “Release title” are the version number (O.x
for major version,0.x.y
for minor and bug fix releases). Release description is the text from PR. Press “Publish release” to finish the process. - Publish the new release on PyPI.