openclaw/nix-openclaw
openclaw/nix-openclaw
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
main
nix-openclaw/maintainers/automation.md
joshp123 5e186c192f docs: split maintainer agent guidance 
Move public maintainer policy and automation guidance into maintainers/, shrink root AGENTS.md into an audience router, and ignore internal .agent scratch state.

Delete tracked internal ExecPlans from .agent and scrub personal/private references from public RFC examples.

Checks: git diff --cached --check; scripts/check-flake-lock-owners.sh; node scripts/select-openclaw-release.test.mjs; bash -n scripts/update-pins.sh; ruby -e 'require "yaml"; YAML.load_file(".github/workflows/yolo-update.yml"); YAML.load_file(".github/workflows/ci.yml")'
2026-05-06 09:29:46 +02:00

1.6 KiB
Raw Permalink Blame History

Maintainer Automation

Maintainer automation is an agentic repair loop for the public packaging pipeline. It is not a second release pipeline and not a private deployment monitor.

Daily Objective

Answer first:

Does nix-openclaw publish the latest upstream version for both supported tracks?

Answer YES only when:

  • openclaw-gateway matches the newest stable upstream source release.
  • openclaw-app matches the newest stable upstream release with a published public OpenClaw-*.zip.

If both tracks are current and yolo/CI are healthy, stop with a short CTO-level report:

  • current gateway
  • latest upstream gateway
  • current app
  • latest published app
  • whether action was needed

Repair Loop

If the desired state is not true, keep working until it is true or until the exact blocker is proven.

Diagnose across:

  • upstream release data
  • yolo selection
  • pin materialization
  • generated config options
  • package builds
  • smoke checks
  • module activation
  • workflow behavior
  • caches
  • CI runner failures

Do not ask for a repair strategy when the desired state is clear.

If the fix belongs in nix-openclaw, edit the repo, self-review the diff until there are no actionable findings, run the relevant targeted checks plus the full gate, commit directly to main, push directly to main, and verify GitHub Actions on the pushed commit.

If upstream has not published public macOS app assets, call that out directly, keep the app pin on the newest public zip, keep packaging the latest stable source-built gateway, and repair nix-openclaw only if it fails to do that.