From 3963d98d7de07d79a76eb3bf5d9e2dca85bff015 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 7 Oct 2017 21:58:52 +0200 Subject: [PATCH] Update instructions --- source/developers/releasing.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/releasing.markdown b/source/developers/releasing.markdown index 2d163ffd6ed..430364cd651 100644 --- a/source/developers/releasing.markdown +++ b/source/developers/releasing.markdown @@ -36,7 +36,7 @@ This page describes the steps for publishing a new Home Assistant release. Those 1. 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. 2. Create missing documentation as stubs. -3. Update `config.yml` with link to the new release blog post and version number (at the bottom of the file). +3. Update `_config.yml` with link to the new release blog post and version number (at the bottom of the file). 4. Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable. 5. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`. DO NOT SQUASH! 6. Run `credits_generator`.