The Astro CLI installation script fails when attempting to install version v1.18.2.

[girishPillai-17]

Describe the bug

The Astro CLI installation script fails when attempting to install version v1.18.2. The installer reports that it cannot find the specified version tag 'v1.18.2' and suggests checking the GitHub releases page for available versions.

The installation script successfully connects to GitHub but cannot locate the specified version tag

root@3749692bab85:/workspace# curl -sSL install.astronomer.io | sudo bash -s -- v1.18.2

astronomer/astro-cli info checking GitHub for tag 'v1.18.2'
astronomer/astro-cli crit unable to find 'v1.18.2' - see https://github.com/astronomer/astro-cli/releases for details

What CLI Version did you experience this bug?

v1.18.2

This CLI bug is related to which Astronomer Platform?

• [x] Astro
• [ ] Software
• [ ] None/Unknown

What Operating System is the above CLI installed on? Tried both and Mac OS Sequoia and Ubuntu

🪜 Steps To Reproduce

1. Run the installation command: curl -sSL install.astronomer.io | sudo bash -s -- v1.18.2
2. The installer begins checking GitHub for the specified tag
3. The installer fails with "unable to find 'v1.18.2'" error
4. Process exits with code 1

📸 Screenshots

[mwojcik321]

We have similar issue:

astronomer/astro-cli info checking GitHub for tag 'v1.34.1'
astronomer/astro-cli crit unable to find 'v1.34.1' - see https://github.com/astronomer/astro-cli/releases for details

which probably is related to the GitHub API limits. After a period of time, the script works again. It would be great to be able to pass the custom GitHub token in order to avoid hitting the limits.

[benjy44]

We noticed the same issue in our github actions after we started to select a specific version (after the 1.35.0 that got borked), we will revert to not select a version since the current latest is back to v1.34.1 but it would be nice to be able to authenticate properly like @mwojcik321 mentioned.

[neel-astro]

This might be an issue due to using a very old CLI version. @girishPillai-17 Is there any chance of upgrading the version? Our support policy is only structured around the last 3 active minor releases. Keeping the CLI version up to date will also help you not run into already resolved bugs and/or security patches.

[Logicnosh]

I noticed the same issue in our github actions after we started to select a specific version after the 1.35.0 that got borked, i will revert to not select a version since the current latest is back to v1.34.1 but it would be nice to be able to authenticate properly like mentioned ig

[neel-astro]

@Logicnosh, can you mention what version you were pinned on? This issue seems to be happening due to API pagination, when someone is trying to use a really older version

[Logicnosh]

Hi @neel-astro, Thanks for the quick response. I was pinned to version v1.18.2 when I encountered the issue. Let me know if you'd like me to test with a more recent version or share any additional details.

— @Logicnosh

On Mon, Jul 21, 2025 at 2:39 PM Neel Dalsania @.***> wrote:

neel-astro left a comment (astronomer/astro-cli#1891) https://github.com/astronomer/astro-cli/issues/1891#issuecomment-3095933069

@Logicnosh https://github.com/Logicnosh, can you mention what version you were pinned on? This issue seems to be happening due to API pagination, when someone is trying to use a really older version

— Reply to this email directly, view it on GitHub https://github.com/astronomer/astro-cli/issues/1891#issuecomment-3095933069, or unsubscribe https://github.com/notifications/unsubscribe-auth/BTCNMKVN4SDZMDHQMETDNUL3JSYN7AVCNFSM6AAAAACBHTBZ6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJVHEZTGMBWHE . You are receiving this because you were mentioned.Message ID: @.***>

[neel-astro]

@Logicnosh, yeah, anything beyond 1.19.0 would work at this moment, but I would recommend using the current latest (1.34.1), and keep the pinned version updated to be one of the last 3 minor releases (since our support policy only covers them)

[mwojcik321]

Hi @neel-astro,

Thank you for your support. I’d like to add that we are using version 1.34.1, and the issue is also occurring.

[neel-astro]

Hi @neel-astro,

Thank you for your support. I’d like to add that we are using version 1.34.1, and the issue is also occurring.

Hmmm, odd, it looks the same on paper, but I believe that might be a different issue, mostly related to the rate limiting that you had pointed out in the earlier comment.

Is it working fine locally/on a new machine, but not working on the CI machine? Then the rate limit would explain that problem, and using GitHub auth token in the CI might help with increasing the rate limits

[mwojcik321]

Then the rate limit would explain that problem, and using GitHub auth token in the CI might help with increasing the rate limits

At the moment, it's not supported by the script? With that in mind, is it possible for this option to be added to the installation script?