Skip to content

ci(workflow-executor): auto-deploy new images to forestadmin-server production#1714

Open
PMerlet wants to merge 1 commit into
mainfrom
ci/workflow-executor-prod-dispatch
Open

ci(workflow-executor): auto-deploy new images to forestadmin-server production#1714
PMerlet wants to merge 1 commit into
mainfrom
ci/workflow-executor-prod-dispatch

Conversation

@PMerlet

@PMerlet PMerlet commented Jun 26, 2026

Copy link
Copy Markdown
Member

After publishing a new stable multi-arch image to GHCR, repository_dispatch forestadmin-server (event_type: workflow-executor-published, payload {version}) so it deploys the image to the production executor environment.

  • Gated on is_latest — only the latest stable version auto-deploys to prod; prereleases and rebuilds of older versions never trigger it.
  • Pairs with ForestAdmin/forestadmin-server#8336, which handles the repository_dispatch (mirror GHCR→ECR + deploy to forestadmin-workflow-executor-production).

Prereq: add a PAT with repo scope on forestadmin-server as the FORESTADMIN_SERVER_DISPATCH_TOKEN secret in this repo.

🤖 Generated with Claude Code

Note

Auto-deploy workflow-executor images to forestadmin-server production on latest release

Adds a step to docker-publish.yml that fires a repository_dispatch event to ForestAdmin/forestadmin-server when a new latest-stable image is published. The dispatch carries a workflow-executor-published event type and the published version, triggering a production deploy in the target repo.

Macroscope summarized e410085.

…le publish

After publishing the multi-arch manifest, repository_dispatch forestadmin-server
(event workflow-executor-published, payload version) so it deploys the new image
to the production executor env. Gated on is_latest — only the latest stable
version auto-deploys to prod; prereleases and older-version rebuilds never do.
Requires a PAT with repo scope on forestadmin-server (FORESTADMIN_SERVER_DISPATCH_TOKEN).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@qltysh

qltysh Bot commented Jun 26, 2026

Copy link
Copy Markdown

Qlty


Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help
  • Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

  • Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

  • File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

    • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant