Interactive: restore AOS CLI release after Telegram alert rollout #762

New issue

Closed

opened 2026-07-27 03:17:43 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-27 03:17:43 +00:00

Member

Outcome

Restore the canonical AOS CLI release pipeline so Scoop can publish the paired aos and aosguard package.

Evidence

The AOS CLI release run at https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/2170 failed in Validate the release commit.
actions-run-one-line rejected 14 Telegram alert run: | block scalars across the eight Forgejo workflows.
The binary build, release asset, Homebrew, and Scoop steps were skipped.
aos-v0.100.0 remains the latest published tag. Windows currently installs the healthy paired package at 0.100.0.

Operator action

The engineer lands the repository-owned single-line or tracked-script alert renderer tracked by #632, without weakening the hook.
The engineer runs the ordinary local validation and pushes the fix once.
An Ops or director run verifies the next aos-cli-release.yml run succeeds, a new aos-v* tag and release assets appear, and the flight-deck Scoop manifest updates.
The operator runs the normal Scoop update and confirms aosguard --version matches the published tag.

The sealed engineer does not rerun or modify live CI.

## Outcome Restore the canonical AOS CLI release pipeline so Scoop can publish the paired `aos` and `aosguard` package. ## Evidence * The AOS CLI release run at https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/2170 failed in `Validate the release commit`. * `actions-run-one-line` rejected 14 Telegram alert `run: |` block scalars across the eight Forgejo workflows. * The binary build, release asset, Homebrew, and Scoop steps were skipped. * `aos-v0.100.0` remains the latest published tag. Windows currently installs the healthy paired package at 0.100.0. ## Operator action 1. The engineer lands the repository-owned single-line or tracked-script alert renderer tracked by #632, without weakening the hook. 2. The engineer runs the ordinary local validation and pushes the fix once. 3. An Ops or director run verifies the next `aos-cli-release.yml` run succeeds, a new `aos-v*` tag and release assets appear, and the `flight-deck` Scoop manifest updates. 4. The operator runs the normal Scoop update and confirms `aosguard --version` matches the published tag. The sealed engineer does not rerun or modify live CI.

coilyco-ops added the

autonomy

live-collab

label

2026-07-27 03:17:43 +00:00

coilyco-ops referenced this issue

2026-07-27 04:41:52 +00:00

Close released AOS composition gaps for inbox#267 #763

coilyco-ops added the

priority

label

2026-07-29 03:45:23 +00:00