Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: cargo-binstall v1.4.1 #1403

Merged
merged 1 commit into from
Sep 26, 2023
Merged

release: cargo-binstall v1.4.1 #1403

merged 1 commit into from
Sep 26, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 26, 2023

This is a release PR for cargo-binstall version 1.4.1 (performing a patch bump).

Use squash merge.

Upon merging, this will automatically create the tag v1.4.1, build the CLI,
create a GitHub release with the release notes below
, and CI will publish to crates.io on merge of this PR.

To trigger builds initially, close and then immediately re-open this PR once.


Edit release notes into the section below:

Release notes

Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for cargo install in most cases. Install it today with cargo install cargo-binstall, from the binaries below, or if you already have it, upgrade with cargo binstall cargo-binstall.

In this release:

  • Initial support for verifying package signatures! (Support package signing and verification #1 Initial signing support #1345 Check quickinstall signatures #1382 Doc: Provide solutions for common problems encountered during signing #1383)

    After a lot of discussions, we now support verifying signatures for downloaded files. This release has support for a single algorithm, minisign. We expect to implement more later, and would warmly welcome contributions in this regard.

    With this comes two new options: --only-signed will refuse to install non-signed packages, and --skip-signatures disables the functionality entirely (for testing only!).

    Adding signature support for your package as a first party requires adding to your Cargo.toml: we don't perform auto-detection of signature schemes at this juncture. Documentation and a guide is available in SIGNING.md.

    The 3rd-party quick-install repository of packages (part of the cargo-bins umbrella organisation) has already implemented signing; if you only want first-party signed packages you should add --disable-strategies quick-install.

  • Binstall's releases are now signed. (Sign our releases #1347 Revert "release: cargo-binstall v1.4.0" and fix #1398 Fix release build again #1400)

    We use a just-in-time ephemeral key or "keyless" setup which generates a brand new signing key for every release.

    You can find the public key for each release in a number of places:

    • in the crate's Cargo.toml metadata (this is where Binstall looks for it)
    • as the minisign.pub file in the packaged source crate (from crates.io)
    • as the minisign.pub file in the downloads below
    • as the minisign.pub file in the .full. variants of the packages below

    Of course, Binstall ^1.4.1 is able to verify its own signature:

    cargo binstall -y --only-signed cargo-binstall

Other changes:

@NobodyXu NobodyXu closed this Sep 26, 2023
@NobodyXu NobodyXu reopened this Sep 26, 2023
@passcod passcod added this pull request to the merge queue Sep 26, 2023
Merged via the queue into main with commit 00941d8 Sep 26, 2023
35 checks passed
@passcod passcod deleted the release/cargo-binstall/1.4.1 branch September 26, 2023 14:25
passcod added a commit that referenced this pull request Sep 26, 2023
github-merge-queue bot pushed a commit that referenced this pull request Sep 26, 2023
* Use explicit write permissions

* Revert "release: cargo-binstall v1.4.1 (#1403)"

This reverts commit 00941d8.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants