fix(ci): build the ARM64 app image on a 16 vCPU runner (#8292)

[waleedlatif1]

• fix(ci): build the ARM64 app image on a 16 vCPU runner (fix(ci): build the ARM64 app image on a 16 vCPU runner #8292)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 25, 2026 8:32am UTC

[greptile-apps]

Confidence Score: 4/5

[High risk] Changes the build runner for ARM64 container images.

The PR appears safe to merge, though validating the new ARM runner label would reduce the risk of a queued GHCR release.

Findings

1.  Unverified ARM runner label ▶

Summary

The PR moves the ARM64 app image build from an 8-vCPU to a 16-vCPU Blacksmith runner.

• The larger runner matches the app build’s documented need for more memory.
• The new main-only runner label should be validated before it becomes part of the release path.

_{Reviews (1) · Last reviewed commit: "fix(ci): build the ARM64 app image on a ..."}

[greptile-apps]

Unverified ARM runner label

This 16-vCPU ARM label is new to the repository, and the build runs only on pushes to main, so PR checks cannot confirm that the runner can take the job. If the label is not provisioned, the app image build will remain queued and block GHCR manifest publication. Please validate the label with a non-release build before relying on it.

Knowledge Base Used: Operations, deployment, and privacy services

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!