macOS binaries - x86_64 and arm64 (apple silicon)

[MikeTheSnowman]

Current Behavior

This issue is simply being raised to create some kind of documentation around this issue. Yesterday, it was discovered that starting with fcli v2.4.0, the native binaries for macOS were unexpectedly being compiled for arm64 (also refered to as either Apple Silicon or M1). Prior to v2.4.0, all our macOS binaries were being compiled for x86_64.

This issue occured because our GitHub workflow is currently configured to use the latest GitHub Hosted runner for macOS (macos-latest). At some point in the past few months, GitHub added a new GitHub hosted runner macos-14 (which used the apple M1 CPU). When that happened, the reference for macos-latest was then updated to point to macos-14. This had the unexpected result in having GraalVM compiling the macOS binaries for arm64 instead of x86-64.

Instructions for fcli users on macOS

• For the mac users that happen to be using fcli on older Intel CPU macOS systems, (at the time of writing this issue) the latest version of fcli that will still work for you is version 2.3.0.
• For mac users that are on Apple Silicon, you won't really be effected as the older x86_64 builds should work because of Rosetta, and the arm64 builds will just work natively.

Future discussions

• For fcli builds, we'll probably need to re-evaluate how we name our release artifacts. For that topic, I'll open up another ticket.
• Because Apple Silicon is the future, I'm not sure if it's worth it to try and produce x86_64 builds of fcli anymore. If there is a serious need, please let us know.

[MikeTheSnowman]

I'm closing this issue as #607 will eventually address this issue. Also, after talking with @rsenden , I've updated the release notes for fcli v2.4 to explain that the macos binary starting from v2.4 will be compiled for apple silicon.