PR Custody

ci: trigger Zen base image rebuild on push to next

@zen-agentchecks n/achecks…feat/zen-image-rebuild-trigger → next1 files · +45 −0updated 3mo ago

▸Description· 1 comment

Description

Adds a GitHub Actions workflow that triggers a Zen Modal image rebuild when integrator code changes are pushed to next. This keeps the sandbox's pre-cloned integrator repo and pre-installed dependencies up to date, so Zen agent sessions start with fresh code.

Trigger paths: cortex/, api/, common/, watchdog/, pyproject.toml, uv.lock

Uses the same GitHub App auth pattern (ZEN_APP_ID + ZEN_APP_PRIVATE_KEY) that hermes and frontend already use.

Required secrets: ZEN_APP_ID and ZEN_APP_PRIVATE_KEY must be added to the integrator repo's secrets (same values used in hermes/frontend).

How did I test this PR

Verified the workflow YAML is valid and follows the same pattern as the existing trigger-zen-rebuild.yml in ComposioHQ/hermes
Confirmed the Zen repo's modal-image.yml already accepts repository_dispatch events of type rebuild-image
Confirmed integrator is already cloned and set up in the Zen base image (images/workspace.py)

🤖 Generated with Claude Code

@zen-agent3mo ago

Review Status

CI Checks ✅

All 5 checks passed on c50af45:

Check	Result
Lint - Integrator	✅ success
Secret Scanning	✅ success
Check File Size	✅ success
Integration Tests	✅ success
Unit Tests - Integrator	✅ success

Codex Review ✅

No correctness issues found. The workflow follows the same pattern already used by hermes and frontend repos.

Reminder: ZEN_APP_ID and ZEN_APP_PRIVATE_KEY secrets must be added to the integrator repo settings before this workflow can run (same values used in hermes/frontend).

🤖 Automated review by Zen Agent

loading diff…