aur-github-publish

Automating AUR publishing from GitHub Actions involves configuring a workflow to detect upstream versions and push PKGBUILD updates to the Arch User Repository. This Skill supports compile-release workflows for your own projects to reduce manual steps.

Yes, you can use GoReleaser integration to update PKGBUILD versions and publish to AUR. This workflow utilizes aurs and aur_sources to automatically synchronize package releases, reducing manual errors during the publication process.

The best way to monitor upstream versions for AUR packages is through an automated version monitoring workflow. This Skill detects upstream updates and synchronizes the PKGBUILD version automatically, requiring manual version entry only when upstream versions cannot be auto-detected.

Yes, the AUR publishing workflow supports manual version entry. When upstream versions cannot be automatically detected by the version monitoring updates, you can manually input the new version to synchronize and publish the PKGBUILD file to AUR.

Setting up an initial AUR publish from a GitHub repository requires a workflow with frontmatter containing the package name and description. The Skill provides initial publish guidance to establish your package on the Arch User Repository via GitHub Actions.

A key limitation when automating PKGBUILD updates is the dependency on auto-detecting upstream versions. If the upstream version cannot be automatically monitored, the workflow requires manual version entry to proceed with publishing the AUR package.