ci: run actions on self-hosted

[cloud-j-luna]

Summary by CodeRabbit

• Chores
  • Updated build and deployment pipeline configurations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Three GitHub Actions workflow files are updated to use self-hosted runner configuration [self-hosted, akash] instead of ubuntu-latest. The runner specification changes from the default GitHub-hosted runner to a custom self-hosted runner group. No workflow logic, steps, or other configurations are modified.

Changes

Cohort / File(s)	Summary
GitHub Actions runner configuration \.github/workflows/build.yml, \.github/workflows/concommits.yml, \.github/workflows/releaser.yml	Updated runner specification from ubuntu-latest to [self-hosted, akash] across all three workflow files

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hops off the cloud so bright,
To runners self-hosted, steady and right,
Akash awaits with a warm embrace,
Three workflows now find their place,
On custom grounds they shall race! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'ci: run actions on self-hosted' clearly and concisely describes the main change across all three workflow files, which involves switching from ubuntu-latest to self-hosted runners.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

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

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/concommits.yml (1)

3-8: Guard self-hosted runners from untrusted PRs (forks).

With pull_request on a self-hosted runner (Line 8), untrusted fork code can run on your infrastructure. Gate PRs to trusted repos or add a fork guard before running jobs.

✅ Suggested guard

 jobs:
   build:
+    if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false
     name: conventional commits
     runs-on: [self-hosted, akash]

♻️ Duplicate comments (2)

.github/workflows/build.yml (1)

7-7: Same self-hosted + pull_request risk applies here.

Please apply the same fork-guard strategy noted in the conventional-commits workflow for Line 7.

.github/workflows/releaser.yml (1)

18-18: Custom runner label still needs actionlint config.

Line 18 uses the same custom label; see the earlier actionlint-label comment.