Automated AUR package updates from a single GitHub repo. Fork it, drop in your packages, let CI handle the rest.

Packages

Auto-generated by CI after each run.

How it works

graph LR
    A[GitHub Actions<br/>on schedule] -->|for each package| B[check-all.sh<br/>run strategy<br/>compare versions]
    B -->|new version found| C[update-pkg.sh<br/>clone AUR repo<br/>sed pkgver<br/>updpkgsums<br/>makepkg --printsrcinfo<br/>git push to AUR]
    B -->|check failed| D[create GitHub Issue<br/>with error details]
    C -->|update failed| D
    C -->|done| E[update-readme.sh<br/>commit badges + status table]

Each package has a YAML config pointing to an upstream source. When a new version is detected, aurtomator clones the existing AUR repo, bumps pkgver, regenerates checksums and .SRCINFO, and pushes. It does not generate PKGBUILDs or modify anything else. If anything fails, a GitHub Issue is opened automatically.

Quick start

1. Fork this repo (or use as template)
2. Enable Actions and Issues in your fork's Settings (why?)
3. Run ./scripts/setup.sh (detailed guide)
4. Add a package: cp packages/example.yml.sample packages/<name>.yml
5. Validate: ./scripts/validate-pkg.sh <name>
6. Push and let CI handle the rest

The setup script configures your identity (git author for AUR commits), SSH access, and GitHub Secrets. If you use gh CLI, secrets are set automatically. Without it, the script prints manual instructions. GPG commit signing is optional.

See docs/SETUP.md for the full setup guide.

Strategies

13 built-in version detection strategies:

See docs/WORKFLOW.md for strategy details, YAML examples, and how to write custom strategies.

Limitations

aurtomator only updates pkgver, checksums, and .SRCINFO. It does not build packages or check dependencies. The following are detected and blocked automatically:

• Split packages -- pkgname=(...) arrays
• pkgver() with wrong strategy -- use git-latest for VCS packages
• Mixed SKIP/real checksums -- updpkgsums is all-or-nothing
• Source URLs returning HTML -- detected via Content-Type check

Packages with patches in source=() trigger a warning but are not blocked.

See docs/SUPPORTED-PACKAGES.md for the full breakdown including safe/unsafe failure modes and comparison with other tools.

Resource usage

All packages run in a single workflow -- one Arch container, one SSH/GPG setup, one run. A version check is one HTTP request per package. This keeps GitHub Actions minutes usage minimal.

Documentation

• Setup guide -- first-time configuration, prerequisites, troubleshooting
• Supported packages -- what works, what doesn't, safety rules
• Workflow reference -- strategies, update process, CI pipeline, local testing, custom strategies

Alternatives

License

BSD-3-Clause