aur-publish
AUR Publish
Update and publish voxtype packages to the Arch User Repository.
Packages
| Package | Type | Location |
|---|---|---|
voxtype |
Source build | packaging/arch/ |
voxtype-bin |
Pre-built binaries | packaging/arch-bin/ |
Prerequisites
- GitHub release already published with binaries
- GPG key configured:
E79F5BAF8CD51A806AA27DBB7DA2709247D75BC6
Workflow for voxtype-bin
1. Generate SHA256 checksums
Download binaries from GitHub release and generate checksums:
VERSION=0.4.14
cd releases/${VERSION}
sha256sum voxtype-${VERSION}-linux-x86_64-avx2
sha256sum voxtype-${VERSION}-linux-x86_64-avx512
sha256sum voxtype-${VERSION}-linux-x86_64-vulkan
2. Update PKGBUILD
Edit packaging/arch-bin/PKGBUILD:
- Update
pkgverto new version - Reset
pkgrelto 1 - Update
sha256sumsarray with new checksums
3. Generate .SRCINFO
cd packaging/arch-bin
makepkg --printsrcinfo > .SRCINFO
4. Test locally
makepkg -si
5. Commit and push to AUR
cd packaging/arch-bin
git add PKGBUILD .SRCINFO
git commit -S -m "Update to ${VERSION}"
git push
Important Rules
Always bump pkgver, never just pkgrel when binaries change.
The download URLs include pkgver:
https://github.com/peteonrails/voxtype/releases/download/v$pkgver/voxtype-$pkgver-linux-x86_64-avx2
If only pkgrel changes, the URL stays the same and AUR helpers cache the old file.
Never re-upload different binaries to an existing GitHub release.
This causes checksum mismatches for users with cached PKGBUILDs.
Checklist
- GitHub release exists with correct binaries
- Binaries verified (version check, instruction validation)
-
pkgverupdated in PKGBUILD -
pkgrelreset to 1 - SHA256 checksums updated
-
.SRCINFOregenerated - Local
makepkg -sisucceeds - Committed with signed commit
- Pushed to AUR
More from peteonrails/voxtype
package-release
Package voxtype for release. Creates deb and rpm packages from binaries. Use when building distribution packages.
22docker-test
Test voxtype in Docker containers. Use for testing builds, verifying packages work on different distros, or isolating test environments.
21regression-test
Run regression tests for voxtype releases. Use before major releases to verify core functionality, CLI commands, and configuration handling.
20update-docs
Update voxtype documentation for releases and features. Use when adding features, fixing bugs, or preparing releases. Covers user manual, troubleshooting, website, release notes, and contributor credits.
20build-release
Build all voxtype binaries for release. Builds Whisper (AVX2, AVX-512, Vulkan) and ONNX (AVX2, AVX-512, CUDA) binaries using Docker. Use when preparing a new release.
18triage
Triage a GitHub issue or PR by checking for duplicates, documentation alignment, project fit, and recommending labels.
17