Verify the first aos-v release after Forgejo runners recover #640

New issue

Closed

opened 2026-07-23 10:32:30 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 10:32:30 +00:00

Owner

The release implementation landed at 2d2807b while Forgejo runners were unavailable. Once runners recover, verify one aos-cli-release run end to end without iterating on live CI: the aos-v tag and Forgejo release exist, all four binaries plus SHA256SUMS and package metadata attach, checksums pass, the Homebrew tap contains Formula/aos.rb, the Scoop bucket contains bucket/aos.json, and both installed packages report the stamped tag through aos version. If live-only state fails, capture the exact run and hand remediation to an ops-capable session.

The release implementation landed at 2d2807b while Forgejo runners were unavailable. Once runners recover, verify one aos-cli-release run end to end without iterating on live CI: the aos-v tag and Forgejo release exist, all four binaries plus SHA256SUMS and package metadata attach, checksums pass, the Homebrew tap contains Formula/aos.rb, the Scoop bucket contains bucket/aos.json, and both installed packages report the stamped tag through aos version. If live-only state fails, capture the exact run and hand remediation to an ops-capable session.

coilyco-ops added the

autonomy

live-collab

label

2026-07-23 10:32:30 +00:00

coilyco-ops referenced this issue from a commit

2026-07-23 10:37:32 +00:00

fix: use the catalog validation verb in aos releases (#640)

coilyco-ops referenced this issue from a commit

2026-07-23 10:46:50 +00:00

fix: sync aos package publication secrets (#640)

coilyco-ops referenced this issue from a commit