fix(packaging): stop publishing an Arch package on every merge to main

arch-package.yml ran on push to main and took its version from `git describe`, so the pacman registry accumulated one package per merge and not one of them corresponded to a version a user could be told to install. It builds the tag release.yml cuts instead. pkgver's literal drops to 0.0.1 with it. That is a downgrade from the 1.x already in the registry, so pacman offers no upgrade and an existing install has to be removed once; epoch=1 would have avoided that and is declined in a comment, because an epoch can never be removed again.
2026-08-17 18:39:06 -04:00
parent 087eb77875
commit 544dbdb4db
2 changed files with 77 additions and 3 deletions
@@ -1,6 +1,17 @@
 # Maintainer: yonlu <yj@yellowjacket.app>
 pkgname=yellowjacket
-pkgver=1.3.0
+# A fallback and the default tag for a manual build; pkgver() below is what
+# actually decides the version, from the clone's own git history.  Versions
+# restarted at 0.0.1 when releases became automatic (plan 017) — which is a
+# *downgrade* from the 1.x packages already in the registry, so pacman offers
+# no upgrade and an existing install has to be removed and reinstalled once:
+#
+#   pacman -R yellowjacket && pacman -S yellowjacket
+#
+# `epoch=1` would have avoided that for one line, and was declined: an epoch
+# can never be removed, and it would put a permanent `1:` in front of every
+# version string this package will ever have.
+pkgver=0.0.1
 pkgrel=1
 pkgdesc="Cross-platform desktop music player — local library, MusicBrainz explore & auto-tag"
 arch=('x86_64')