Bump version to v1.15.2

Use new commit sha for release

.github/workflows/bump-version.yml

@@ -17,12 +17,16 @@ jobs:
         python-version: '3.x'
     - run: pip install -r script/requirements.txt
     - run: script/bump-version.py ${{ github.event.inputs.version }}
-    - run: |
+    - name: Commit version bump
+      id: commit_version
+      run: |
         git config user.name esphomebot
         git config user.email contact@esphome.io
         git add .
         git commit -m "Bump version to v${{ github.event.inputs.version }}"
         git push
+        COMMIT=$(git rev-parse HEAD)
+        echo "::set-output name=commit_sha::${COMMIT}"
     - if: ${{ contains(github.event.inputs.version, 'b') }}
       name: Create Beta Release
       uses: actions/create-release@v1
@@ -33,6 +37,7 @@ jobs:
         release_name: ${{ github.event.inputs.version }}
         body: 'See https://beta.esphome.io/changelog/index.html'
         prerelease: true
+        commitish: ${{ steps.commit_version.outputs.commit_sha }}  
     - if: ${{ !contains(github.event.inputs.version, 'b') }}
       name: Create Stable Release
       uses: actions/create-release@v1
@@ -43,6 +48,7 @@ jobs:
         release_name: ${{ github.event.inputs.version }}
         body: 'See https://esphome.io/changelog/index.html'
         prerelease: false
+        commitish: ${{ steps.commit_version.outputs.commit_sha }} 
 
 
   deploy-community-addons:

esphome-beta/README.md

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
 
 Manually override which ESPHome version to use in the add-on.
 For example to install the latest development version, use `"esphome_version": "dev"`,
-or for version 1.14.0: `"esphome_version": "v1.14.0""`.
+or for version 1.14.0: `"esphome_version": "v1.14.0"`.
+
+This can also be used to specify a branch of a fork of the esphome repository.
+For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
+This usage assumes the forked repository is named `esphome`.
 
 Please note that this does not always work and is only meant for testing, usually the
 ESPHome add-on and dashboard version must match to guarantee a working system.

esphome-beta/config.json

@@ -42,6 +42,6 @@
   "stage": "experimental",
   "startup": "application",
   "url": "https://beta.esphome.io/",
-  "version": "1.15.0b4",
+  "version": "1.15.2",
   "webui": "http://[HOST]:[PORT:6052]"
 }

esphome-dev/README.md

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
 
 Manually override which ESPHome version to use in the add-on.
 For example to install the latest development version, use `"esphome_version": "dev"`,
-or for version 1.14.0: `"esphome_version": "v1.14.0""`.
+or for version 1.14.0: `"esphome_version": "v1.14.0"`.
+
+This can also be used to specify a branch of a fork of the esphome repository.
+For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
+This usage assumes the forked repository is named `esphome`.
 
 Please note that this does not always work and is only meant for testing, usually the
 ESPHome add-on and dashboard version must match to guarantee a working system.

esphome/README.md

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
 
 Manually override which ESPHome version to use in the add-on.
 For example to install the latest development version, use `"esphome_version": "dev"`,
-or for version 1.14.0: `"esphome_version": "v1.14.0""`.
+or for version 1.14.0: `"esphome_version": "v1.14.0"`.
+
+This can also be used to specify a branch of a fork of the esphome repository.
+For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
+This usage assumes the forked repository is named `esphome`.
 
 Please note that this does not always work and is only meant for testing, usually the
 ESPHome add-on and dashboard version must match to guarantee a working system.

esphome/config.json

@@ -1,7 +1,6 @@
 {
   "arch": [
     "amd64",
-    "i386",
     "armv7",
     "aarch64"
   ],
@@ -27,7 +26,7 @@
     "6052/tcp": null
   },
   "ports_description": {
-    "6052/tcp": "Web interface (Not required for Hass.io Ingress)"
+    "6052/tcp": "Web interface (Not required for Home Assistant Ingress)"
   },
   "schema": {
     "certfile": "str?",
@@ -40,8 +39,9 @@
     "streamer_mode": "bool?"
   },
   "slug": "esphome",
+  "stage": "stable",
   "startup": "application",
   "url": "https://esphome.io/",
-  "version": "1.14.5",
+  "version": "1.15.2",
   "webui": "http://[HOST]:[PORT:6052]"
 }

template/README.md

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
 
 Manually override which ESPHome version to use in the add-on.
 For example to install the latest development version, use `"esphome_version": "dev"`,
-or for version 1.14.0: `"esphome_version": "v1.14.0""`.
+or for version 1.14.0: `"esphome_version": "v1.14.0"`.
+
+This can also be used to specify a branch of a fork of the esphome repository.
+For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
+This usage assumes the forked repository is named `esphome`.
 
 Please note that this does not always work and is only meant for testing, usually the
 ESPHome add-on and dashboard version must match to guarantee a working system.

template/config.yaml

@@ -56,7 +56,7 @@ esphome-beta:
   <<: *base
   directory: esphome-beta
   name: ESPHome (beta)
-  version: '1.15.0b4'  # BETA
+  version: '1.15.2'  # BETA
   slug: esphome-beta
   description: "Beta version of ESPHome Hass.io add-on."
   url: https://beta.esphome.io/
@@ -68,7 +68,7 @@ esphome-stable:
   <<: *base
   directory: esphome
   name: ESPHome
-  version: '1.14.5'  # STABLE
+  version: '1.15.2'  # STABLE
   slug: esphome
   description: "ESPHome Hass.io add-on for intelligently managing all your ESP8266/ESP32 devices."
   image: esphome/esphome-hassio-{arch}