fix(installer): avoid latest release API lookup - #46
Merged
Conversation
Signed-off-by: Sri Aradhyula <sraradhy@cisco.com>
sriaradhyula
marked this pull request as ready for review
August 13, 2026 21:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
latestthe installer default in the repositoryCAIPE_VERSIONsupport for immutable version-pinned installsRoot cause
The installer queried the unauthenticated GitHub Releases API only to discover the newest tag. GitHub can rate-limit that endpoint with HTTP 403 even though the public release assets remain downloadable.
Validation
shellcheck install.shbunx tsc --noEmitbun run lint(passes with 18 existing warnings)bun run test(224 tests)0.2.22