From c131a37a2465132f301d8e18b234876748082213 Mon Sep 17 00:00:00 2001 From: Timothy <6560631+TimoPtr@users.noreply.github.com> Date: Mon, 28 Jul 2025 10:02:16 +0200 Subject: [PATCH] Migrate from tag to pre-release to push changelog update --- docs/android/ci.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/android/ci.md b/docs/android/ci.md index fae87705..bba0b207 100644 --- a/docs/android/ci.md +++ b/docs/android/ci.md @@ -90,9 +90,9 @@ They use the `version_code.txt` file, which is created on every release from the We do not guarantee when the applications will be available on F-Droid after a release. You can find the app [on F-Droid](https://f-droid.org/packages/io.homeassistant.companion.android.minimal/). ::: -### On tag +### On pre-release -When a tag that matches the [CalVer] versioning format is pushed, the `onTag.yml` workflow is triggered. This workflow generates a new pull request with an updated `changelog_master.xml` file reflecting the new version. Manual approval of this pull request is required. This process helps keep the changelog version aligned with the app version. +When a release is created in `pre-release` state, the `onPrereleased.yml` workflow is triggered. This workflow generates a new pull request with an updated `changelog_master.xml` file reflecting the new version. Manual approval of this pull request is required. This process helps keep the changelog version aligned with the app version. ## Summary of workflows @@ -103,7 +103,7 @@ When a tag that matches the [CalVer] versioning format is pushed, the `onTag.yml | `weekly.yml` | Every Sunday at 4:00 AM | Create a pre-release and push the beta build to the Play Store. | | `monthly.yml` | First day of the month | Create an initial version tag (`YYYY.MM.0`). | | `release.yml` | Manual trigger | Promote the beta build to production. | -| `onTag.yml` | On tag matching [CalVer] | Update `changelog_master.xml` in a PR. | +| `onPrereleased.yml` | On pre-release | Update `changelog_master.xml` in a PR. | ---