Files
inbuxa-installer/cmd
jcoffey-dev b6f11f0d6c
ci / test (pull_request) Successful in 55s
Add pin-check: catch release pins that have fallen behind upstream
A fresh install ships whatever internal/release/release.go names, so a
pin left behind is a fresh install shipped stale -- and, when the release
it skipped fixed a vulnerability, shipped vulnerable. The server, console
and webmail pins have each gone stale before.

pin-check reads each component's releases from the Gitea API and reports
when the pinned version is behind the newest release in its channel. The
channel follows the pin: a candidate pin (27.1-rc.15) tracks newer 27.1
candidates and the 27.1 final, and the check stays in the pin's own
major.minor series -- a later flagship (27.2) or the parallel
calendar-versioned maintenance line (2026.x) the suite ships alongside
is a deliberate move to a new installer line, not a pin bump.

It only reads; it never edits release.go. The move stays a reviewed
change with the new checksums taken from each release's signed
SHA256SUMS. The tool exits 10 when anything is stale, so the weekly
.gitea/workflows/pin-check.yml run turns a stale pin into a red run and,
with --issue, a self-updating tracking issue.

The version/compare/channel logic is a pure, unit-tested package; the
command's API reads and exit codes are covered with an httptest server.
Stdlib only.
2026-11-12 11:03:20 -07:00
..