docs: clarify 1.0.3→1.0.5 version lineage and refresh AUR workflow

Explain why 1.0.4 is a git tag while 1.0.5 is the verified GitHub release.
Trigger AUR publish on releases and via workflow_dispatch; bump PKGBUILD base.
This commit is contained in:
Sebastian Palencsar
2026-06-21 09:02:06 +02:00
parent d42aa5e043
commit 72b4c35669
4 changed files with 15 additions and 4 deletions

View File

@@ -11,7 +11,9 @@ BearWave is designed for fast station browsing, simple playback controls, favori
![License: GPL--3.0--or--later](https://img.shields.io/badge/license-GPL--3.0--or--later-lightgrey)
![Version](https://img.shields.io/badge/version-1.0.5-blue)
**Current release:** [1.0.5](CHANGELOG.md#105---2026-06-20) (2026-06-20) — includes [1.0.4](CHANGELOG.md#104---2026-06-20) security/stability/QML refactor plus CI test fixes.
**Current release:** [1.0.5](CHANGELOG.md#105---2026-06-20) (2026-06-20)
Why not 1.0.4 on GitHub? [1.0.4](CHANGELOG.md#104---2026-06-20) exists as a **git tag** (security, stability, QML refactor) but was tagged before CI passed. **1.0.5** is the first verified GitHub release after [1.0.3](CHANGELOG.md#103---2026-05-30). See [version notes](CHANGELOG.md#version-notes-103--105) in the changelog.
## Screenshots