Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/operations/lazurio-fork-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -234,7 +234,7 @@ Organization Admin can do these steps; the order matters.
`prevent_self_review`, deployments from `main` only, variable
`LAZURIO_OPENMAUSBOT_RELEASE_CONTROL=reviewed-v1`, variable
`LAZURIO_RELEASE_APP_ID`, secret `LAZURIO_RELEASE_APP_PRIVATE_KEY`.
8. **First release** `0.1.91-lazurio.1`, dispatched by the Steward.
8. **First release** `0.1.91-lazurio.1`, dispatched by the Steward. Right after it, disable the upstream workflows it registered (Automation boundary).

## Testing before a release

Expand Down Expand Up @@ -364,3 +364,14 @@ gh workflow list --repo Lazurio/OpenMausBot --all --json id,path,state \
Only `lazurio-fork-ci.yml` (read-only; required check), `lazurio-archive.yml`
(called by both others) and the manually dispatched `lazurio-release.yml`
stay active.

GitHub registers a workflow only at its first triggering event, and only a
registered workflow can be disabled. After the one-time bootstrap (2026-09-30)
`docker.yml` and `ci-stop-closed.yml` registered and are disabled. `docker.yml`
fired on the bootstrap push and ended in `startup_failure`, because Actions
allow only GitHub-owned actions plus `pnpm/action-setup`. `npm-package.yml`
(tag `v*`) and `sync-published-release.yml` (release published) register only
with the first release, and neither can publish from this fork: npm does not
trust this repository for `openmausbot`, and the mirror needs `RELEASES_PAT`.
Right after the first release, run the disable command above, and check that
nothing but the three `lazurio-*` workflows is active (issue #6).