68fa648010
Implements the last unimplemented pipeline stage from SPEC.md: PKGBUILD
generation + makepkg (builder.rs), a post-build version sanity check
(sanity.rs), and repo-add publishing (publisher.rs), wired into main.rs
for both the tier 1-3 auto-publish path and a new tier 4-6 review queue
(`pkgwatch review` / `pkgwatch review <name> --approve`, persisted via
state::{load,save,clear}_pending_version, tracked separately from
last-published-version since approving one release isn't a standing
auto-publish grant for future ones).
Publishing targets an existing, already-registered local pacman repo
(~/.local/share/pacman/custom, `[custom]` in /etc/pacman.conf) rather
than one pkgwatch invents — found already in real use for a hand-packaged
AppImage, which resolves SPEC's open question on where the repo lives
without pkgwatch ever touching pacman.conf. Publishing stops at
`repo-add`; actually installing/upgrading (`pacman -Syu`/`pacman -S`) is
left to the operator, not run automatically.
Getting a real second package (scaleway-cli, tier 4) through the new
pipeline immediately surfaced a real gap: its pacman package is named
`scaleway-cli` but the actual binary is `scw` (confirmed via `pacman -Ql`
against the currently-installed extra package) — without a way to
declare that, the build would install alongside extra's package under
the wrong name instead of shadowing it. Added `Package::binary_name`
(config.rs) to cover it.
Every upstream-controlled string (version, asset name, download URL)
is validated before it touches generated shell content in the PKGBUILD
template — rejects anything containing a single quote or newline, since
values are embedded in single-quoted bash strings.
Verified for real, end to end: uv (tier 2) auto-built and published
against the real astral-sh/uv release with no human step; scaleway-cli
(tier 4) queued for review, then approved via `pkgwatch review
scaleway-cli --approve`, which re-verified, built, and published it —
confirmed the built package contains exactly usr/bin/scw. Both landed in
the real custom repo's database. Left scaleway-cli's real-repo review
pending rather than approving it myself: the tier 4-6 gate exists for a
human judgment call, not the agent's.
69 tests, cargo make ci clean (fmt, clippy, complexity, coverage, audit).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
28 lines
1.2 KiB
TOML
28 lines
1.2 KiB
TOML
# Verified 2026-09-17 against the real repo: scaleway/scaleway-cli does not
|
|
# publish GitHub build-provenance attestations (the attestations API 404s
|
|
# for a fresh release asset) — tier 4, same-origin checksum only, not tier
|
|
# 2. Motivation: Manjaro's `extra` scaleway-cli lags upstream by weeks;
|
|
# this tracks upstream releases directly instead.
|
|
#
|
|
# Releases ship one combined `SHA256SUMS` file (one line per platform
|
|
# asset) rather than a per-asset checksum file like uv's — verifier
|
|
# matches the line by filename.
|
|
#
|
|
# binary_name = "scw": confirmed by checking the currently-installed
|
|
# `extra` package (`pacman -Ql scaleway-cli`) — the pacman package is
|
|
# named scaleway-cli but the actual binary it installs is `scw`. Without
|
|
# this, pkgwatch's build would install as /usr/bin/scaleway-cli, which
|
|
# would NOT shadow extra's /usr/bin/scw at all.
|
|
|
|
[package.scaleway-cli]
|
|
repo = "scaleway/scaleway-cli"
|
|
asset_pattern = "scaleway-cli_{version}_linux_amd64"
|
|
binary_name = "scw"
|
|
|
|
[package.scaleway-cli.verification]
|
|
method = "same-origin-sha256"
|
|
checksum_asset_pattern = "SHA256SUMS"
|
|
|
|
[package.scaleway-cli.sanity_check]
|
|
command = "scw version"
|
|
version_regex = 'Version\s+(\d+\.\d+\.\d+)'
|