Skip to content

automation.md

Latest commit

 

History

History
55 lines (37 loc) · 1.52 KB

automation.md

File metadata and controls

55 lines (37 loc) · 1.52 KB

Automation

Current Automatic Path

The repo can advance itself without any upstream changes.

sync-from-public-release.yaml does this:

  1. Inspect the latest public release in BrowserBox/BrowserBox
  2. Check whether bbx Saga Test Suite (Public Release) succeeded for that tag
  3. If the latest release failed saga, fall back to the newest release tag with a successful public saga
  4. Regenerate package-manager metadata
  5. Commit the new state back to main

This keeps the repo safe even when a public release exists but the public install surface is not healthy yet.

Ideal Future Path

The low-latency version is a dispatch from the public saga workflow after success.

Suggested sender:

  • repo: BrowserBox/BrowserBox
  • workflow: .github/workflows/bbx-saga.yaml
  • event: send repository_dispatch to BrowserBox/BrowserBox-distribution

Suggested payload:

{
  "event_type": "browserbox_release_ready",
  "client_payload": {
    "tag": "v16.2.8",
    "source_repo": "BrowserBox/BrowserBox",
    "source_workflow": "bbx Saga Test Suite (Public Release)"
  }
}

Suggested token shape:

  • scope it to BrowserBox/BrowserBox-distribution only
  • use it only from the sender workflow
  • keep the current scheduled polling path as fallback

Why The Repo Does Not Auto-Publish Everywhere

The current goal is packaging surface exploration, not ecosystem publication.

So this repo:

  • generates and versions manifests
  • builds Linux package artifacts
  • does not auto-submit Homebrew, Chocolatey Community, or nixpkgs updates