revert: undo ARM migration and multi-arch changes in semaphore pipelines

[Yashprime1]

Summary

Revert all ARM (Graviton) migration changes introduced via the update-agent-to-arm branch.

What is reverted

• Agent types: c6g → c5, t4g → t2 (back to x86)
• Binaries: ARM variants → x86 variants (uv, Go, Node.js, JDK, etc.)
• Docker builds: Multi-arch docker buildx → original single-arch docker build (where applicable)
• cfstack: cfstack-arm → cfstack (where applicable)

---

Note

Medium Risk
CI/CD infrastructure change that can break builds/deploys if the selected x86 agent images or downloaded binaries don’t match runtime expectations.

Overview
Reverts Semaphore CI/CD agent selection from ARM/Graviton to x86 by switching machine types (t4g→t2, c6g→c5) across build, staging deploy, and production deploy pipelines.

Updates deploy scripts to download and use the x86_64 uv tarball (and PATH) instead of the aarch64 variant, keeping the rest of the S3/CloudFront deployment flow unchanged.

^{Written by Cursor Bugbot for commit 2968329. This will update automatically on new commits. Configure here.}

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline infrastructure configurations to optimize build and deployment processes across staging and production environments.

[francispereira]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 523c25d and 2968329.

📒 Files selected for processing (3)

• .semaphore/production-deploy.yml
• .semaphore/semaphore.yml
• .semaphore/staging-deploy.yml

---

📝 Walkthrough

Walkthrough

Configuration updates to Semaphore CI deployment pipelines switching agent machine types from ARM-based to x86-based instances and updating UV tool binaries from aarch64 to x86_64 architecture across production, staging, and general pipeline stages.

Changes

Cohort / File(s)	Summary
Semaphore CI Agent Configuration .semaphore/production-deploy.yml, .semaphore/staging-deploy.yml, .semaphore/semaphore.yml	Agent machine type changes from ARM instances (s1-agent-c6g-large, s1-agent-t4g-micro) to x86 equivalents (s1-agent-c5-large, s1-agent-t2-micro) across all deployment stages.
UV Tool Binary Architecture .semaphore/production-deploy.yml, .semaphore/staging-deploy.yml	UV toolchain tarball source updated from aarch64 to x86_64 architecture (uv-aarch64-unknown-linux-gnu.tar.gz → uv-x86_64-unknown-linux-gnu.tar.gz) with corresponding PATH exports adjusted.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• PR #512: Directly reverses these changes, switching agent types and UV architecture back from x86 to ARM in the same configuration files.
• PR #397: Modifies the same Semaphore CI configuration files with agent machine type updates across staging and production workflows.
• PR #495: Updates the same Semaphore pipeline files to change agent machine types and swap UV runtime tarball to x86_64 build.

Suggested reviewers

• singhkunal2050
• darshanclevertap

Poem

🐰 From ARM to x86, the agents take flight,
Swapping their cores from aarch64 to x86 might—
CI pipelines ready in staging and prod,
New machine types deployed by the CI god!
🚀✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provides a clear summary and detailed explanation of changes, but does not follow the repository's required template structure with mandatory sections like 'Changes', 'Testing', and 'Checklist'.	Restructure the description to include required template sections: Changes (with Jira reference), Changes to Public Facing API, How Has This Been Tested, Checklist items, and deployment/automation trigger instructions.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: reverting ARM migration and multi-arch changes in semaphore pipelines, which aligns directly with the actual file modifications.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch revert-arm-change

---

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