ci: use GitHub-hosted runners in fork

[michaelmwu]

Summary

• replace inherited private Depot runner labels with GitHub-hosted runners across CI, Console CI/audit, docs, PR audit, and chart release workflows
• make the 508-dev fork's checks executable instead of leaving jobs queued forever for runners the organization does not own
• leave image publishing untouched here because PR ci: publish pilot images to 508-dev GHCR #4 replaces that workflow with the fork-specific protected GHCR publisher

Verification

• actionlint passes for all six edited workflows when ignoring the pre-existing SC2155 warning in ci.yml
• diff contains runner-label substitutions only

---

Note

Low Risk
Runner-label substitutions only; no application, secret, or test logic changes, with possible CI duration or queue behavior differences on GitHub-hosted runners.

Overview
Replaces private Depot runner labels with ubuntu-latest across six GitHub Actions workflows so CI can run on forks that do not have access to organization-owned runners.

Affected jobs include main CI path-filtered work (migration order, harness-server, rust-api, slackbotv2, discordbot, githubbot, teamsbot), Console CI (Brakeman, importmap audit, RuboCop, tests), Console gem audit, docs build/deploy, PR audit (cyclops label), and Helm chart release. Job steps, triggers, and conditions are unchanged—only runs-on values differ.

publish-images is not modified here (fork-specific GHCR publishing is handled separately).

^{Reviewed by Cursor Bugbot for commit 455d16e. Bugbot is set up for automated code reviews on this repo. Configure here.}

Summary by CodeRabbit

• Chores
  • Updated continuous integration, testing, auditing, documentation, and release workflows to use the standard Ubuntu runner.
  • Existing workflow steps and deployment behavior remain unchanged.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_12958350-4c4b-41d8-9987-adf7275b61d8)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1ef2b7df-eec9-48a4-927f-8bc1ed39d569

📥 Commits

Reviewing files that changed from the base of the PR and between ccd6ed8 and 455d16e.

📒 Files selected for processing (6)

• .github/workflows/ci.yml
• .github/workflows/console-ci.yml
• .github/workflows/console-gem-audit.yml
• .github/workflows/docs.yml
• .github/workflows/pr-audit.yml
• .github/workflows/release-chart.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

All listed GitHub Actions workflows replace the depot-ubuntu-24.04-16 runner with ubuntu-latest. Job steps and workflow behavior remain unchanged.

Changes

Runner migration

Layer / File(s)	Summary
CI workflow runners .github/workflows/ci.yml, .github/workflows/console-ci.yml	The main CI and Console CI jobs now run on ubuntu-latest.
Supporting workflow runners .github/workflows/console-gem-audit.yml, .github/workflows/docs.yml, .github/workflows/pr-audit.yml, .github/workflows/release-chart.yml	Audit, documentation, pull request audit, and chart release jobs now run on ubuntu-latest.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 455d1

This change moves CI jobs to GitHub-hosted runners so fork checks can execute; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: mslipper, zygimantass

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: replacing private Depot runners with GitHub-hosted runners for fork CI workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch use-github-hosted-runners

---

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.}