Add `amplify-pkg-macos-arm64.tgz` in GitHub Releases

[eggplants]

Is this feature request related to a new or existing Amplify category?

No response

Is this related to another service?

No response

Describe the feature you'd like to request

Please add amplify-pkg-macos-arm64.tgz to Releases for Apple Silicon Mac.

Describe the solution you'd like

It seems necessary to add a process to build a Mach-O 64-bit executable with the arm64 architecture to the workflow in AWS CodeBuild BuildBatch us-east-1 (Release).

Describe alternatives you've considered

Currently, pre-built binaries for Darwin in the latest release are only available for x86_64, amplify-pkg-macos.tgz, and require Rosetta 2 in Mac computers with Apple silicon.

Alternatively, we can install it using npm install -g @aws-amplify/cli.

Additional context

I encountered this issue while attempting to install amplify-cli via mise.

Is this something that you'd be interested in working on?

• [ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

• [ ] ⚠️ This feature might incur a breaking change

[pahud]

Hi @eggplants,

Thank you for this feature request! Yes, native ARM64 support for macOS would significantly improve the experience for developers using Apple Silicon Macs. I can confirm that our current release process only builds x86_64 binaries for macOS (which require Rosetta 2), while we do provide native ARM64 binaries for Linux. This inconsistency should be addressed.

The technical implementation appears straightforward since:

• We already have ARM64 build infrastructure (evidenced by amplify-pkg-linux-arm64.tgz)
• The @yao-pkg/pkg tool we use supports node22-macos-arm64 targets
• The build script just needs to be updated to include the ARM64 macOS target

I believe this would involve updating our build script to:

1. Add the node22-macos-arm64 target to the generatePkgCli function
2. Update the upload process to include the new ARM64 binary
3. Adjust size verification thresholds

We appreciate you bringing this to our attention, I am labeling this a feature request and please help us prioritize with 👍