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

@@ -3,6 +3,9 @@ name: Publish to AUR
on:
push:
branches: [ main ]
release:
types: [ published ]
workflow_dispatch:
jobs:
aur-publish:

View File

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
## Version notes (1.0.3 → 1.0.5)
- **1.0.3** — last GitHub release before the security/refactor batch.
- **1.0.4** — git tag with security hardening, playback/tray/MPRIS fixes, and QML refactor; tagged before CI was green, so it was not published as a GitHub release at first.
- **1.0.5** — current recommended release: everything in 1.0.4 plus headless CI test fixes.
## [1.0.5] - 2026-06-20
### Fixed

View File

@@ -1,6 +1,6 @@
# Maintainer: Sebastian Palencsar <moin@nerdbear.de>
pkgname=bearwave-git
pkgver=1.0.3
pkgver=1.0.5
pkgrel=1
pkgdesc="KDE-focused desktop internet radio app"
arch=('x86_64')
@@ -17,7 +17,7 @@ pkgver() {
cd "${srcdir}/${pkgname%-git}"
# Holt das letzte Tag (z.B. 1.0.1), die Anzahl der Commits danach und den Hash
git describe --long --tags 2>/dev/null | sed 's/^v//;s/\([^-]*-\)g/r\1/;s/-/./g' || \
printf "1.0.3.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
printf "1.0.5.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}
build() {

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