aur-publish
This tool automates AUR package distribution by updating files, generating checksums, and pushing repository changes.
Install
mkdir -p .claude/skills/aur-publish && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3680" && unzip -o skill.zip -d .claude/skills/aur-publish && rm skill.zipInstalls to .claude/skills/aur-publish
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Publish voxtype to AUR. Updates PKGBUILD, generates checksums, and pushes to AUR. Use after a GitHub release is published.Key capabilities
- →Update PKGBUILD files
- →Generate SHA256 checksums
- →Regenerate .SRCINFO
- →Push changes to AUR
How it works
It automates the update of package versioning, checksum generation, and metadata synchronization between GitHub releases and the Arch User Repository.
Inputs & outputs
When to use aur-publish
- →Publishing binary updates to AUR
- →Updating checksums for new releases
- →Synchronizing GitHub release with Arch packages
About this skill
AUR Publish
Update and publish voxtype packages to the Arch User Repository.
Packages
| Package | Type | Tracks | Location |
|---|---|---|---|
voxtype | Source build | Latest stable tag | packaging/arch/ |
voxtype-bin | Pre-built binaries | Latest stable release | packaging/arch-bin/ |
voxtype-bin-rc | Pre-built binaries | Latest pre-release tag | packaging/arch-bin-rc/ |
All three are nested git repos inside the main checkout's packaging/
directory (gitignored there; each pushes to ssh://aur.archlinux.org/<name>.git).
Prerequisites
- GitHub release already published with the full asset set and
SHA256SUMS.txtuploaded (CI signs it with9CCF7915B750CAE8B095ED1AA3FC9F33FD209279) - AUR maintainer GPG key configured:
E79F5BAF8CD51A806AA27DBB7DA2709247D75BC6
Checksums: the rules (learned the hard way at 1.1.0)
- The CI-signed
SHA256SUMS.txtfrom the release is the only source of truth for binary sums. Never trust a locally downloaded file's hash on its own - cross-check every non-SKIP sum in the PKGBUILD against that file before pushing. - Do not let
updpkgsumsrewrite this PKGBUILD. It strips the per-entry comments (which are load-bearing) and has left orphan lines that break sourcing. Use it at most to download the sources, then write sums yourself. source_x86_64andsource_aarch64share local filenames (voxtype-$pkgver-osdnames both arches' downloads). Hashing local files therefore poisons the aarch64 array with x86_64 sums. Take the aarch64 sums fromSHA256SUMS.txtby remote filename, never from disk..ascentries areSKIP(signatures are verified viavalidpgpkeys). The source tarball is not in SHA256SUMS.txt: hash the downloaded tarball, thengpg --verifyits.ascto prove the hash is of the authentic file.
Workflow for voxtype-bin
VERSION=1.1.0
cd packaging/arch-bin
# 1. Bump version
sed -i "s/^pkgver=.*/pkgver=${VERSION}/; s/^pkgrel=.*/pkgrel=1/" PKGBUILD
# 2. Fetch the authoritative sums
curl -sL "https://github.com/peteonrails/voxtype/releases/download/v${VERSION}/SHA256SUMS.txt" -o /tmp/sums.txt
# 3. Update every sums array from /tmp/sums.txt by REMOTE filename,
# preserving the comments (script it; do not use updpkgsums to write).
# Raw-file sources (config.toml, service, completions, LICENSE, README,
# desktop entry, launcher) are fetched at the tag and hashed locally.
# 4. Cross-check: every non-SKIP binary sum in the PKGBUILD must appear in
# /tmp/sums.txt. Zero misses or stop.
# 5. Update the post_upgrade highlights in voxtype-bin.install for the new
# version. The banner header reads pacman's $1 - never hardcode a
# version in that file (a hardcoded 1.0.0 announced 1.1.0's features).
# 6. Regenerate, verify, push
makepkg --printsrcinfo > .SRCINFO
bash -n PKGBUILD && bash -n voxtype-bin.install
git add PKGBUILD .SRCINFO voxtype-bin.install
git commit -S -m "Update to ${VERSION}"
git push
Workflow for voxtype (source package)
Same shape, two sources: the GitHub archive tarball (hash it, then
gpg --verify the release's .asc against it) and its signature (SKIP).
The tag must carry a Cargo.lock matching Cargo.toml's version or
cargo fetch --locked fails for every builder (the v0.4.6 incident).
Workflow for voxtype-bin-rc
Tracks pre-release tags. AUR forbids hyphens in pkgver, so v1.2.0-rc1
becomes pkgver=1.2.0.rc1 and the PKGBUILD's _upstream_ver computes the
real tag back (${pkgver/.rc/-rc}). Everything else follows the
voxtype-bin workflow against the pre-release's SHA256SUMS.txt. Note: as of
1.1.0 this package has never been published; its first push creates it.
Important Rules
Always bump pkgver, never just pkgrel, when binaries change. The
download URLs include pkgver only; a pkgrel-only bump leaves the URL
unchanged and AUR helpers serve cached files against new checksums.
pkgrel bumps are for packaging-only changes (install script, deps).
Never re-upload different binaries to an existing GitHub release. Cut a new version instead.
Checklist
- GitHub release exists, all assets uploaded, SHA256SUMS.txt present
- Binaries validated (/validate-binaries; baseline needs the behavioral floor test, not just --version)
-
pkgverbumped,pkgrelreset to 1 - Every binary sum cross-checked against the CI-signed SHA256SUMS.txt
- aarch64 sums taken from SHA256SUMS.txt, not from local files
- Tarball hash GPG-verified against its .asc
- post_upgrade highlights updated (no hardcoded versions)
-
.SRCINFOregenerated;bash -npasses on PKGBUILD and .install - Committed signed, pushed to AUR
When not to use it
- →When the GitHub release binaries are not yet published
- →When re-uploading different binaries to an existing release
Prerequisites
Limitations
- →Requires manual GPG key configuration
- →Must bump pkgver for binary changes
How it compares
It ensures versioning and checksums are correctly synchronized to prevent AUR helper caching issues.
Compared to similar skills
aur-publish side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| aur-publish (this skill) | 1 | 10mo | Review | Intermediate |
| github-release-management | 4 | 9mo | Review | Advanced |
| macos-spm-app-packaging | 1 | 8mo | Review | Intermediate |
| hex-release | 2 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by peteonrails
View all by peteonrails →You might also like
github-release-management
ruvnet
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
macos-spm-app-packaging
Dimillian
Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.
hex-release
agentjido
Guides interactive Hex package release. Bumps version in mix.exs, updates CHANGELOG with commits, creates git tag. Triggers on: release, hex publish, bump version, new release.
agent-release-swarm
ruvnet
Agent skill for release-swarm - invoke with $agent-release-swarm
magerun-release
netz98
Technical release process for n98-magerun2
release
ziggy42
Use this skill when the user wants to cut a new release.