fix(ci): publish docker images for stable tags

- publish standalone Docker images from all version tags
- align release docs with stable tag publishing behavior

Author: awesomestvi

.github/workflows/publish.yml

@@ -5,9 +5,7 @@ on:
     branches:
       - main
     tags:
-      - 'v*-alpha.*'
-      - 'v*-beta.*'
-      - 'v*-rc.*'
+      - 'v*'
   workflow_dispatch:
     inputs:
       version:

README.md

@@ -162,8 +162,8 @@ volumes:
   navet-data:
 ```
 
-`latest` tracks the current public beta tag. Pushes to `main` publish developer images as `dev` and
-`sha-*`, so production-style deployments should use `latest`, `beta`, or a specific prerelease tag
+`latest` tracks the current public release tag. Pushes to `main` publish developer images as `dev` and
+`sha-*`, so production-style deployments should use `latest`, `beta`, or a specific release tag
 instead of expecting `main` to update `latest`.
 
 Start Navet:

docs/DOCKER_HOME_ASSISTANT_ADDON.md

@@ -114,10 +114,10 @@ Then open `http://localhost:8080`.
 The GitHub Actions publish workflow publishes multi-arch app images to GitHub Container Registry:
 
 - pushes to `main`: `ghcr.io/<owner>/navet:dev` and `ghcr.io/<owner>/navet:sha-<commit>`
-- public prerelease tags (`v*-alpha.*`, `v*-beta.*`, `v*-rc.*`): exact tag, `beta`, `latest`, and `sha-*`
+- public release tags (`v*`): exact tag, `beta`, `latest`, and `sha-*`
 - manual workflow runs: the requested developer tag, defaulting to `dev`, plus `sha-*`
 
-`latest` is the current public beta compatibility tag. It is updated by prerelease tags, not by
+`latest` is the current public release compatibility tag. It is updated by release tags, not by
 ordinary `main` pushes.
 
 ### GHCR Deployment

docs/VERSIONING.md

@@ -62,7 +62,7 @@ Recommended lightweight flow:
 6. For add-on releases, bump `addons/navet/config.yaml` and update `addons/navet/CHANGELOG.md`.
 7. If the release meaning changed, update this file.
 8. Tag the commit with a version tag such as `v0.1.1-beta.1` or `v0.1.1`.
-9. Push the tag to GitHub to trigger [.github/workflows/github-release.yml](../.github/workflows/github-release.yml). Prerelease tags also trigger app image publishing and add-on image publishing.
+9. Push the tag to GitHub to trigger [.github/workflows/github-release.yml](../.github/workflows/github-release.yml). Version tags also trigger app image publishing and add-on image publishing.
 10. For developer hardware testing before a public tag, manually run the publish workflows with the `dev` tag.
 
 ## Release Note Style