Heads up —

install.sh

in master appears to be broken against the current

latest

tarball, so CI pipelines using the canonical curl-pipe-sh install are failing. The script ends with:

mv /tmp/infracost-$os-$arch /usr/local/bin/infracost

but the tarball at

<https://infracost.io/downloads/latest/infracost-linux-amd64.tar.gz>

now contains a binary named just

infracost

, with no platform suffix:

$ curl -sL <https://infracost.io/downloads/latest/infracost-linux-amd64.tar.gz> -o /tmp/i.tgz
$ tar tzf /tmp/i.tgz
infracost

Result in CodeBuild logs:

Moving /tmp/infracost-linux-amd64 to /usr/local/bin/infracost ...
mv: cannot stat '/tmp/infracost-linux-amd64': No such file or directory

Checksum validation passes (so the .sha256 was regenerated to match the new archive), and

set -e

doesn't trip on the

tar xzf

, which confirms the archive is structurally fine — just laid out differently than install.sh expects. Looks like the artifacts at

/downloads/latest/

got re-uploaded with a different internal layout without a corresponding install.sh update. Anyone else seeing this? Ally deploys at my company are now broken. This step has always worked for 4.5 years. Happy to open a GitHub issue if it's not already on the radar.

Hey @calm-grass-70658 - sorry about that, that install script was not intended for use in CI/CD pipelines, it was for installing the Infracost CLI on dev machines. We’re in the process of releasing a major new version of the CLI and so that script was updated to install that for new users who are installing the CLI on their laptops. Can you possibly update your pipeline to fix your CLI version to the old one? it’s https://github.com/infracost/infracost/releases/tag/v0.10.44

I'll just rm it completly thanks.