ci: migrate release workflows to ci-infra runners

[yongwww]

📌 Description

Migrate self-hosted runner labels from the old always-on EC2 instances to the new ephemeral runners managed by ci-infra.

🔍 Related Issues

🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull request, please make sure the following items are complete.

✅ Pre-commit Checks

• I have installed pre-commit by running pip install pre-commit (or used your preferred method).
• I have installed the hooks with pre-commit install.
• I have run the hooks manually with pre-commit run --all-files and fixed any reported issues.

If you are unsure about how to set up pre-commit, see the pre-commit documentation.

🧪 Tests

• Tests have been added or updated as needed.
• All tests are passing (unittest, etc.).

Reviewer Notes

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline configurations to optimize resource allocation and execution environments across multiple release workflows, improving build and test scheduling efficiency.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[coderabbitai]

📝 Walkthrough

Walkthrough

GitHub Actions workflow files are updated to standardize runner selectors across three workflows. Runner specifications are expanded to include explicit labels (linux, cpu, on-demand) and replace platform identifiers with consistent architecture mapping (arm64 for aarch64, x64 otherwise) for improved self-hosted runner targeting and scheduling.

Changes

Cohort / File(s)	Summary
Workflow Runner Configuration .github/workflows/nightly-release.yml, .github/workflows/release-ci-docker.yml, .github/workflows/release.yml	Updates runs-on selectors across multiple jobs to use standardized labels: replace platform identifiers (x86_64, X64, G5) with explicit linux, x64, arm64 (conditional), cpu, and on-demand tags. Expands matrix-driven runner selection for improved self-hosted runner matching.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• yzh119
• cyx-6

Poem

🐰 Runners align with labels true,
Linux, x64, arm64 too!
On-demand and cpu they stand,
Workflows now span the promised land! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: migrating release workflows to ci-infra runners, which matches the core objective of updating runner labels across workflow files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description addresses the main change (migrating runner labels), completes most checklist items, and follows the template structure well.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[yzh119]

Hi @yongwww can you explain how we trigger CI after this change?

[yongwww]

Hi @yongwww can you explain how we trigger CI after this change?

The CI triggering mechanism remains the same, no changes needed on the workflow trigger side.

When any workflow is triggered (push, PR, schedule, or manual dispatch), GitHub automatically sends a workflow_job webhook event when jobs are queued. The ci-infra system receives this webhook via API Gateway → Lambda, which then launches an ephemeral EC2 runner on-demand to execute the job.

[yzh119]

@yongwww thanks for explaination.

[yzh119]

@flashinfer-bot run