[BUG] flytectl/install.sh doesn't work with old versions because they are too far back in release page

[tgreen7]

Flyte & Flytekit version

flytectl v0.8.19

Describe the bug

We are using flytectl version v0.8.19 which was working up until recently. I think the install script filtering on release pages doesn't get older versions. Seems like it only retrieves back to v0.8.24 now that other packages releases have been pushed.

flyteorg/flyte info checking GitHub for tag 'v0.8.19'
flyteorg/flyte info found version: hello
"flytectl/v0.9.5"
"flytectl/v0.9.4"
"flytectl/v0.9.2"
"flytectl/v0.9.1"
"flytectl/v0.9.0"
"flytectl/v0.8.24" for hello
"flytectl/v0.9.5"
"flytectl/v0.9.4"
"flytectl/v0.9.2"
"flytectl/v0.9.1"
"flytectl/v0.9.0"
"flytectl/v0.8.24"/Darwin/arm64

error:

flyteorg/flyte info checking GitHub for tag 'v0.8.19'
flyteorg/flyte crit unable to find 'v0.8.19' - use 'latest' or see https://github.com/flyteorg/flyte/releases for details

Could you update the script to make sure old releases will still work properly?

Expected behavior

Be able to use any release version of any package.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

It seems likely that the flytectl install.sh script currently only retrieves a limited number of recent releases from the GitHub releases API, which means older versions like v0.8.19 may not be available for installation if they are no longer included in the first page of results. This is a known limitation of how GitHub's API paginates release tags, and the script does not appear to handle pagination or search for older tags beyond the most recent set. As a result, attempting to install or reference older versions may fail with an "unable to find" error, as you observed.

My understanding is that this limitation is not explicitly addressed in the available documentation or scripts, and there is no mention of a workaround or update to the install.sh script to ensure all historical releases are accessible. You may need to manually download the desired binary from the GitHub releases page if it is not found by the script. Would you like more detail on how to manually install an older flytectl version or on possible script improvements?

Sources:

• flytectl release process

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[0yukali0]

#take