Skip to content

Release workflow

GitHub Actions validates the source, packages every platform on its own native runner, and only publishes a GitHub Release once every packaging job succeeds.

AgentDock Pro

This describes AgentDock Pro's .github/workflows/release.yml. AgentDock's public repository does not currently run the same native multi-platform release pipeline — see Known limitations.

Triggers

  • workflow_dispatch — a manual run that builds artifacts (via gh workflow run release.yml --ref <branch> or the Actions tab) without publishing anything.
  • A v* tag push — runs the full pipeline and, if every packaging job succeeds, publishes a GitHub Release from the built artifacts.
  • Pull requests touching release-relevant files (the workflow itself, electron-builder.yml, package.json/package-lock.json, or the packaging scripts) exercise the pipeline without publishing.

Jobs

  1. Validate — npm ci, typecheck, tests, and a production build, on a native Windows runner.
  2. Windows / Linux / macOS Intel / macOS Apple Silicon — four independent packaging jobs, each on its own native runner (windows-latest, ubuntu-latest, macos-15-intel, macos-15) — no cross-compilation.
  3. GitHub release (tag pushes only) — runs after every packaging job succeeds, publishing the built artifacts as a GitHub Release using the workflow's own token; electron-builder itself never touches GitHub Releases (publish: null).

Every trigger except a tag push uploads workflow artifacts only — a release is published exclusively by pushing a vX.Y.Z tag.

Related