bootintel-cli v0.14.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.13.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.12.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.9.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.8.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.11.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.10.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.7.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli

bootintel-cli v0.6.1

Withdrawn. Use 0.7.0 instead, which is the same code.

This release made scan history opt in, which changes a default. A user upgrading on a patch would have found bootintel history silently stopped recording, and the project's versioning policy reserves PATCH for changes with no user-visible behaviour change. Renumbered to 0.7.0 so the version itself carries the warning.

The crates.io version is yanked. Nothing is wrong with the binaries here; the number was wrong.

bootintel-cli v0.6.0

Release notes: see CHANGELOG.md.

This is a DRAFT — publish manually after verifying artifacts.

Verify what you downloaded

Checksums are in SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

Every archive also carries a signed build-provenance attestation,
so you can confirm it was produced by this repository's release
workflow rather than by someone's laptop:

gh attestation verify <archive> --repo BootIntel/cli