Add rb list --remote and answer --version - #12
Merged
Conversation
Probing an unknown rb with --version is how a caller identifies the build it got, and answering that with usage and a non-zero exit reads as a broken binary rather than as an old one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The binary index is the only way to learn what can be installed, and so far a caller had to fetch and parse index.json to see it. The output is the counterpart of `rb list`: name, channel, and the tags `install` takes, newest first. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The schema number is the only channel the feed has for telling an old rb that it is old, and "upgrade rb" left the reader to work out which rb had answered and where a newer one comes from. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
rb --versionandrb -Vfell through to usage and exited 2, so probing an unknown binary looked like a broken one rather than an old one. Seeing what the index offers meant fetching and parsingindex.jsonby hand, which makes it easy to miss thatrb install ruby-devexists at all.Both flags now print the same line as
rb version.rb list --remoteprints the builds the index offers for this platform, newest first, with the tagsinstallaccepts. The unknown-schema error now names the running build and the releases page, which is the only signal the feed has for telling an oldrbthat it is old.The index currently carries only dev snapshots, so the README's
rb install 4.0.5example does not resolve yet. That is ruby/actions' side.Generated with Claude Code