Repository navigation
Conversation
bootintel-detectors and bootintel-cli are both on crates.io at 0.4.1. Verified end to end rather than from the workflow's exit code: cargo install bootintel-cli --locked into a clean root produces a 0.4.1 binary that exits 2 on an empty capture, 3 on unrecognized input, detects a timestamped U-Boot banner, and survives a pipe into head. That is the fix set, reached through the public index. The README keeps the install one-liner first and notes that the cargo path builds from source, so it needs a toolchain and takes minutes where the prebuilt binary takes seconds. Both are real options and the faster one leads. This is the step docs/releasing.md held back until a publish had actually succeeded, for the reason that made three advertised channels dead ends: an install command that fails reads as an abandoned project. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by the rename: the README install line lands in that branch as |
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.
Both crates are live on crates.io at 0.4.1.
Verified end to end rather than from the workflow's exit code:
That is the whole fix set, reached through the public index.
The README keeps the install one-liner first and notes that the cargo path builds from source, so it needs a toolchain and takes minutes where the prebuilt binary takes seconds.
This is the step
docs/releasing.mddeliberately held back until a publish had actually succeeded, for the reason that made three advertised channels dead ends: an install command that fails reads as an abandoned project.