Repository navigation
fix(install): add cargo-binstall metadata and recommend --locked - #1454
Merged
Merged
Conversation
Without [package.metadata.binstall], cargo-binstall guesses a release asset name that does not match ours and falls back to compiling from source, which re-resolves dependencies and can pick up broken upstream releases. Point it at the published per-platform archives, and document `cargo install --locked` so source installs use the tested dependency set. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Maxim Stykow <maxim.stykow@gmail.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
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
[package.metadata.binstall]socargo binstall provenant-clidownloads our prebuilt release archives instead of falling back to a source build.cargo install --locked provenant-cliin the README.Issues
defined_namesin initializer ofDocumentIR" error inpdf_oxide#1453 (mitigation; the compile error itself is upstream,pdf_oxide 0.3.78vsoffice_oxide 0.1.13, fixed inpdf_oxide0.3.79 which is not yet published)Scope and exclusions
cargo installwork again once published.How to verify
cargo binstall --manifest-path . --dry-run --no-confirm --disable-strategies compile provenant-cli@1.0.14resolves and downloads the release archive from GitHub (checked on aarch64-apple-darwin). Takes effect for users from the next release.🤖 Generated with Claude Code