changer git runner from blacksmith to ubuntu

[rapoler]

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions release pipeline infrastructure configuration for improved build consistency.

[claude]

Claude finished @rapoler's task —— View job

---

PR Review: GitHub Actions Runner Migration

I'll review this pull request that changes GitHub Actions runners from "blacksmith" to "ubuntu-latest".

Review Tasks:

• Analyze workflow file changes
• Check for consistency across all files
• Evaluate security implications
• Assess performance considerations
• Review for potential bugs or issues
• Check test coverage impact

Analysis Complete

I've analyzed all 4 workflow files and their changes. Here's my comprehensive review:

✅ Code Quality & Best Practices

Consistent Changes: All 4 files show the same pattern:

• blacksmith-4vcpu-ubuntu-2404 → ubuntu-latest
• Applied uniformly across all workflows

Good Migration Pattern: The change is clean and follows GitHub Actions best practices by using the standard ubuntu-latest runner.

⚠️ Potential Performance Considerations

Performance Impact:

• Loss of 4vCPU specification: blacksmith-4vcpu-ubuntu-2404 explicitly provided 4 vCPUs, while ubuntu-latest uses GitHub's standard 2vCPU runners
• Build time increase expected: Docker builds and Go compilation may take longer with reduced CPU resources
• Impact on workflows:
  • .github/workflows/server-prod.yaml:10 - Go builds will be slower
  • All workflows with Docker builds will see increased build times

Recommendation: Consider using ubuntu-latest-4-cores or ubuntu-latest-8-cores if build performance is critical.

🔍 No Security Concerns

• ubuntu-latest is GitHub's official runner image
• No changes to permissions or secrets handling
• Standard GitHub-hosted runners are regularly updated and secure

✅ No Bugs or Issues Detected

• All syntax is correct
• Runner specifications are valid
• No broken references or dependencies

ℹ️ Test Coverage Impact

No Direct Impact: This change only affects the runner environment, not test execution logic. However:

• Tests will run on potentially different Ubuntu versions (ubuntu-latest vs fixed blacksmith image)
• May need verification that all dependencies work on the new runner

📋 Summary

Pros:

• ✅ Simplified maintenance (no custom runner dependency)
• ✅ Cost reduction (GitHub-hosted vs potentially paid blacksmith runners)
• ✅ Consistent with GitHub Actions standards

Cons:

• ⚠️ Reduced CPU resources (4vCPU → 2vCPU)
• ⚠️ Potential build time increases

Overall Assessment: ✅ Approved with Performance Note

This is a clean, well-executed migration. The main consideration is the performance trade-off from reduced CPU resources.

---

[coderabbitai]

Walkthrough

Four GitHub Actions workflow files are updated to replace the self-hosted runner "blacksmith-4vcpu-ubuntu-2404" with the generic "ubuntu-latest" runner. No workflow logic, steps, or control flow modifications.

Changes

Cohort / File(s)	Summary
GitHub Actions Runner Updates .github/workflows/chat-server.yaml, .github/workflows/server-prod.yaml, .github/workflows/web-app.yaml, .github/workflows/web-prod.yml	Replaced self-hosted runner label "blacksmith-4vcpu-ubuntu-2404" with ubuntu-latest in release jobs. All workflow steps and logic remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Homogeneous change pattern applied consistently across all four files
• Simple runner label substitution with no behavioral impact
• No logic modifications or workflow step changes

Possibly related PRs

• add chat-server, server-prod, web-prod git actions #14: Modifies the same GitHub Actions workflow files (chat-server.yaml, server-prod.yaml, web-app.yaml, web-prod.yml) with runner label changes.

Poem

🐰 The runner hops from blacksmith's forge so grand,

To ubuntu plains, a simpler land,

No logic stirred, just labels freed,

Our workflows dance with newfound speed! ✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and clearly describes the main change: replacing the GitHub Actions runner from a specific self-hosted runner (blacksmith) to ubuntu-latest across all workflow files.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/changerunner

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a67035b and 218af6a.

📒 Files selected for processing (4)

• .github/workflows/chat-server.yaml (1 hunks)
• .github/workflows/server-prod.yaml (1 hunks)
• .github/workflows/web-app.yaml (1 hunks)
• .github/workflows/web-prod.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (go)

🔇 Additional comments (4)

.github/workflows/chat-server.yaml (1)

11-11: Runner switch to ubuntu-latest is appropriate for this Docker build workflow.

The change from the self-hosted blacksmith-4vcpu-ubuntu-2404 runner to GitHub-hosted ubuntu-latest is straightforward and suitable for Docker build/push operations. The workflow has no custom tool dependencies that would require the self-hosted runner.

Please confirm that the workflow has been tested with ubuntu-latest and successfully builds and pushes the image. If there are any cached dependencies or environment-specific tools from the blacksmith runner that this workflow relied on, please verify they are available on ubuntu-latest or adjust the workflow accordingly.

.github/workflows/server-prod.yaml (1)

10-10: Runner switch to ubuntu-latest is appropriate for this Go + Docker workflow.

The change from blacksmith-4vcpu-ubuntu-2404 to ubuntu-latest is suitable for this workflow. Go is explicitly configured via actions/setup-go@v2 (line 25), so there's no reliance on pre-installed tooling from the self-hosted runner, and the module caching strategy is compatible with ubuntu-latest.

Please verify that:

1. The workflow has been tested and successfully builds the Go projects and Docker images on ubuntu-latest.
2. There are no custom environment variables or tools from the blacksmith runner that were relied upon (e.g., special Go configurations, custom Docker setup).

Note for future improvement: Consider upgrading actions/setup-go@v2 to a newer version (v4 or v5) for improved performance and compatibility, though this is outside the scope of this PR.

.github/workflows/web-prod.yml (1)

11-11: Runner switch to ubuntu-latest is appropriate for this web app Docker workflow.

The change from blacksmith-4vcpu-ubuntu-2404 to ubuntu-latest is suitable. This workflow only requires Docker and basic Linux utilities, both available on ubuntu-latest. No custom dependencies from the self-hosted runner are evident.

Please confirm that the workflow has been tested with ubuntu-latest and successfully builds and pushes the web app Docker image.

.github/workflows/web-app.yaml (1)

11-11: Runner switch to ubuntu-latest is appropriate for this Docker build workflow.

The change from the self-hosted blacksmith-4vcpu-ubuntu-2404 runner to ubuntu-latest is straightforward and suitable. This workflow requires only Docker and standard Linux utilities, both available on ubuntu-latest, with no reliance on custom tools from the self-hosted runner.

Please verify that the workflow has been tested with ubuntu-latest and successfully builds and pushes the web app Docker image.

---

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