This ER is related to issue #606.
We may want to consider updating the name convention of the fcli native binary build artifacts to also include the cpu architecture in the file name. The macOS ecosystem is currently in transition from x86_64 (Intel) to ARM (Apple Silicon/M1), Linux is commonly used with ARM (and possibly RISC-V), and there is a growing base of Windows on ARM as well.
As an example, if we ever product a build of fcli for Linux on ARM, the build artifact file name could be fcli-linux-arm64.tgz. For the x86_64 builds, we can probably just leave the file names as-is so that we don't accidentally break anything.
Enhancement Request
This ER is related to issue #606. We may want to consider updating the name convention of the fcli native binary build artifacts to also include the cpu architecture in the file name. The macOS ecosystem is currently in transition from x86_64 (Intel) to ARM (Apple Silicon/M1), Linux is commonly used with ARM (and possibly RISC-V), and there is a growing base of Windows on ARM as well. As an example, if we ever product a build of fcli for Linux on ARM, the build artifact file name could be
fcli-linux-arm64.tgz. For the x86_64 builds, we can probably just leave the file names as-is so that we don't accidentally break anything.