Skip to content

Publish AUR package nightly - #41

Merged
Jbsco merged 3 commits into
mainfrom
feat/aur-release
Nov 3, 2026
Merged

Jbsco merged 3 commits into
mainfrom
feat/aur-release

Conversation

@Jbsco

@Jbsco Jbsco commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

Keeps the AUR package blockcodec-bin at the latest release with a nightly workflow. No other project of mine does this yet.

  • aur.sh sets a package clone's pkgver, pkgrel and SHA-256 to a release, writes .SRCINFO, builds the package from its release tarball, commits, and pushes with --push. It reads the package name from its clone, so another project's -bin package can use it unchanged.
  • .github/workflows/aur.yml runs nightly and by hand once the repository variable AUR_PACKAGE is set. A first job compares the latest release with the AUR version through the AUR's RPC interface and reads the release's SHA-256. Only when they differ does a second job run aur.sh in archlinux:base-devel as an unprivileged user. That job pins the AUR's ED25519 host key and reads its SSH key from a secret of the aur environment, which deploys from main only.
  • README.md gives AUR install commands and how the workflow works.

Nightly batches several releases a day into one AUR update and retries a failed push on its own; release.yml is unchanged. Its ED25519 key is dedicated to this workflow, generated here and stored only as that environment secret.

Verification: aur.sh left an already packaged version alone, failed without a commit on a missing release, and built and committed a real bump to 0.1.0. Steps of the update job ran in an archlinux:base-devel container up to the push, which needs the key. The comparison found nothing to do for blockcodec-bin at v0.1.0 and gave version and SHA-256 for a package the AUR lacks. style.do passes.

@Jbsco Jbsco changed the title Update AUR package after release Publish AUR package nightly Nov 3, 2026
@Jbsco
Jbsco merged commit aab7b13 into main Nov 3, 2026
3 checks passed
@Jbsco
Jbsco deleted the feat/aur-release branch November 3, 2026 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant