# 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+)'