Skip to content

ci: run manual-release workflow on warp 16x runner#210

Merged
dimittal merged 1 commit intomainfrom
ci/manual-release-warp-runner
Apr 28, 2026
Merged

ci: run manual-release workflow on warp 16x runner#210
dimittal merged 1 commit intomainfrom
ci/manual-release-warp-runner

Conversation

@dimittal
Copy link
Copy Markdown
Contributor

Summary

  • Bumps the runner for the `release` job in `.github/workflows/manual-release.yaml` from `ubuntu-latest` (2-core, 7GB) to `warp-ubuntu-latest-x64-16x-spot` (the same pool used by the `setup` job in `build-and-push.yaml`).
  • The release job builds a multi-arch image (`linux/amd64,linux/arm64`) and pushes to DockerHub + GHCR; on the alpine base several Python deps compile from source, so the stock runner is the bottleneck.
  • No functional change to what gets built or where it gets pushed.

Test plan

  • Trigger `Manual Release` from the Actions tab with a test version (or wait for the next intentional release) and confirm the runner shows as `warp-ubuntu-latest-x64-16x-spot` in the run logs.
  • Confirm the resulting images appear in DockerHub + GHCR with the expected tags.
  • Confirm the helm chart push to `oci://ghcr.io/drdroidlab/charts` still succeeds when `push_helm_chart=true`.

🤖 Generated with Claude Code

The release job builds a multi-arch (linux/amd64,linux/arm64) image
and pushes it to DockerHub + GHCR. Stock ubuntu-latest (2-core, 7GB)
makes this painfully slow, especially for the alpine base where
several Python deps compile from source. Bumps the runner to the
same warp pool used elsewhere in CI.

No functional change to what gets built or where it's pushed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@dimittal dimittal merged commit 15a6859 into main Apr 28, 2026
2 checks passed
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.

2 participants