OXYGENHUB

Docs: the rollback report the hub holds a build on; runner updates' status 8aa45fa6ece5

refs #84, oxygenhub#326
Author
Andy McCall @andymccall <[email protected]>
via
agent agent:claude@andymccall <[email protected]> · keyless, under your grant for changes,refs,seal · key 5c1b206fbe3a
When
· 2026-10-26 04:35 UTC
Signature
◈ sealed by agent:claude@andymccall
Hash
8aa45fa6ece5691294638e6bfaa7c3dc2ca491e2a486709df0b91d233f4f7d7b
Depends on
2814f4213e7c 494a1b9a8ac2 85275e1ef3b7 a083cc802892 c90dd8d5fc36
Depended on by
nothing yet
In bookmarks
main
In tags
v0.4.0 v0.5.0 v0.5.1 v0.5.2 v0.5.3
Edits
4 atoms, 0 tree operations, 2 files

Browse the tree at this change

hide whitespace changes
modified docs/jetstream.md +8 −3
… 
373 unchanged lines
374 374 

    

  
    

      375
      375
       
      
**Order of work:** (1) the runner side, with a local source (`flow runner

    

  
    

      376
      376
       
      
update --from FILE`): check, stage, drain, swap, prove, roll back (done,

    

  
    

      377
      
      -
      
#85: spec §11.5.3); (2) the

    

  
    

      
      377
      +
      
#85: spec §11.5.3, Linux and Windows); runners asking the hub and taking

    

  
    

      
      378
      +
      
its offer (done); (2) the

    

  
    

      378
      379
       
      
policy on the hub (opt in and out, channels, windows, dry run) and the

    

  
    

      379
      
      -
      
update in the claim answer; (3) test groups, waves and health; (4) the

    

  
    

      380
      
      -
      
swarm as transport; (5) Admin › Runners › Updates and `oh runner update`.

    

  
    

      
      380
      +
      
update a runner is offered (done: oxygenhub#322, for the site and for each

    

  
    

      
      381
      +
      
organisation's own runners, `GET /api/v1/flow/runner/update`); (3) test groups (done: chosen or a percentage), waves and health (a

    

  
    

      
      382
      +
      
build that rolls back on one runner is held for every other, oxygenhub#326;

    

  
    

      
      383
      +
      
waves that advance by themselves after a soak are not built yet); (4) the

    

  
    

      
      384
      +
      
swarm as transport; (5) Admin › Runners › Updates (done) and `oh runner

    

  
    

      
      385
      +
      
update`.

    

  
    

      381
      386
       
      

    

  
    

      382
      387
       
      
## 9. Pools

    

  
    

      383
      388
       
      

    

  
    

      
      
      …
      
166 unchanged lines

    

  
  

  





  
    modified
    docs/spec.md
    +4 −0
  
  
  

  
    

      
      
      …
      
882 unchanged lines

    

  
    

      883
      883
       
      
   on the fourth start without that answer, or after ten minutes running

    

  
    

      884
      884
       
      
   without it, `flow.prev` is put back (and on a start, run in its place).

    

  
    

      885
      885
       
      
   `updates.log` in the home records every install, proof and rollback.

    

  
    

      
      886
      +
      
   The runner tells the hub at its next answer (`POST /api/v1/flow/runner/update`):

    

  
    

      
      887
      +
      
   `runs flow X (was Y); proven`, or `rolled back from flow X to Y: why`,

    

  
    

      
      888
      +
      
   on which the hub holds X back from every other runner until an

    

  
    

      
      889
      +
      
   administrator lifts the hold (oxygenhub#326).

    

  
    

      886
      890
       
      
6. **On Windows** (oxygenflow#83) the same steps run with Windows' means:

    

  
    

      887
      891
       
      
   the build is checked as a PE executable for this machine; `flow.exe`

    

  
    

      888
      892
       
      
   is renamed to `flow.prev.exe` and `flow.new.exe` into its place (a

    

  
    

      
      
      …
      
20 unchanged lines