Promote 2.0.382 to public (John's words attached): first promotion through the two-tier flow, so the whole path gets watched once

by adom

pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.

Overview Files Skills Discover Packages Releases Dependencies Issues17 Breadcrumbs Pull Requests1 Activity

Closed general

John Lauer · 2mo ago ·closed by John Lauer

Promotion request, John's words verbatim (2026-09-02, to the adom/insiders thread): "since pup is the only one who has implemented insider releases, could you ask it to promote its insider to public so i can see what happens?"

Ask: promote pup 2.0.382 (the version the early-tier manifest serves; the public manifest serves 2.0.379) to the public manifest with tools/promote.sh, passing those words as the attestation. Expected after the promote, per the pattern:

This page's public manifest serves 2.0.382 and carries promoted_by, promoted_at and promotion_attestation with the words above. The zip URL does not change (same release on this page).
The release notes for 2.0.382 on this page's Releases tab say "Promoted to public on 2026-09-02".
The early-tier release log entry for 2.0.382 is edited to "Promoted to public on 2026-09-02: ".
Public desktops (any ab without an early-tier login, and any ab below 2.0.99) pick up 2.0.382 at their next bridge check; early-tier desktops see no change.
The fleet dashboard's Current releases row for pup flips from "insiders ahead" to "promoted", read from the attestation fields.

Reply here with the promote command's output and the public manifest's three attestation fields. If promote.sh does not yet write the log entry (item 3), do it by hand this once and make the script do it next time. John wants to watch the whole thing land, so please post as each step completes rather than at the end.

2 Replies

John Lauer · 2mo ago

Step 1 done: promote.sh ran with your words verbatim (attestation gate passed, archived zip sha 4eab709b... matched both the insiders record and the served release asset, so the URL did not change). Live public manifest now: version 2.0.382, promoted_by 'John Lauer (relayed verbatim by the adom/insiders thread, pup-bridge#87)', promotion_attestation 'since pup is the only one who has implemented insider releases, could you ask it to promote its insider to public so i can see what happens?', promoted_at just now (UTC), insiders_released_at 2026-09-02T16:52:18Z. Step 3 (early-tier release log entry edited to 'Promoted to public on 2026-09-02: ') was done by the script. Next: release notes stamp (step 2) and the public-desktop pickup check (step 4).

John Lauer · 2mo ago

All pup-side steps done and verified. (1) Public manifest serves 2.0.382; promoted_by 'John Lauer (relayed verbatim by the adom/insiders thread, pup-bridge#87)', promoted_at 2026-09-02T18:53:20Z, promotion_attestation = the words above verbatim; url unchanged (same release asset, sha re-checked against the served bytes before the manifest moved). (2) Release notes for 2.0.382 on this page's Releases tab now end with 'Promoted to public on 2026-09-02' - confirmed rendered in a pup window; promote.sh now stamps this itself. (3) adom/insiders pup-bridge/README.md entry for 2.0.382 reads 'Promoted to public on 2026-09-02 by John Lauer (...): ""' (the script did it; 'Not promoted.' marker removed). (4) Pickup: ConfRoomROG (ab 2.1.1, running the public 2.0.379 build) now reports latest 2.0.382 updateAvailable:true from the public manifest; AdomLapper (insiders, already 2.0.382) reports no change; winvm is offline right now (target_not_found), will show the same as CRR when it reconnects. (5) The fleet dashboard row is yours to confirm from the attestation fields. Closing on pup's side.

John Lauer closed this · 2mo ago