Download dist 0.31.0

Release Notes
This release includes several new features, including the major introduction of mirrors that installers can fallback to.
Simple hosting (aka mirrors)
This release adds a new hosting method, simple, which supports static file hosting. This allows you to host your artifacts on the hosting provider of your choice so long as it follows a similar URL structure to GitHub Releases hosting. It can also be used alongside GitHub hosting; if you specify more than one hosting provider, the secondary hosting source will be used as a mirror. The priority is determined by the order of the keys in your config. For example, this will use GitHub first and fall back to your static host if GitHub is unavailable:
hosting = ["github", "simple"]
simple-download-url = "https://static.myapp.com/{tag}"
And this will use your static host first and fall back to GitHub if necessary:
hosting = ["simple", "github"]
simple-download-url = "https://static.myapp.com/{tag}"
For more information, see the docs.
Note: currently, dist won't upload artifacts to static hosts; it expects you to handle that, either manually or via writing a custom job.
- impl @Gankra Add "simple" hosting style
- impl @mistydemeo feat(homebrew): mirror support with multi-urls
Disabling npm-shrinkwrap.json for npm installers
Currently, the npm installer includes an npm-shrinkwrap.json to specify the exact versions of its runtime dependencies as used at the time dist was released. Since some users would prefer looser dependency specification, this release provides an option to disable this. For more information, see the docs.
npm-shrinkwrap = false
- impl @mistydemeo feat: option to skip npm-shrinkwrap.json generation
Configurable build directory for generic projects
Until now, generic (non-Rust) project support has assumed that artifacts are always written to the root of the project directory. This path is now configurable using the out-dir setting in your dist.toml. For example, if your project generates a binary named example in a subdirectory called build, you can specify:
binaries = ["example"]
out-dir = "build"
- impl @CatBraaain support out_dir in config
Fixes
- impl @EliteTK + @Gankra Reduce risk of an interrupted installation leading to a partial installation
Install cargo-dist 0.31.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/axodotdev/cargo-dist/releases/download/v0.31.0/cargo-dist-installer.sh | sh
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/axodotdev/cargo-dist/releases/download/v0.31.0/cargo-dist-installer.ps1 | iex"
Install prebuilt binaries via Homebrew
brew install axodotdev/tap/cargo-dist
Install prebuilt binaries into your npm project
npm install @axodotdev/dist@0.31.0
Download cargo-dist 0.31.0
─────────────────────────────────────────────────┬───────────────────┬─────────────
File │Platform │Checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-aarch64-apple-darwin.tar.xz │Apple Silicon macOS│checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-x86_64-apple-darwin.tar.xz │Intel macOS │checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-x86_64-pc-windows-msvc.zip │x64 Windows │checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-aarch64-unknown-linux-gnu.tar.xz │ARM64 Linux │checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-x86_64-unknown-linux-gnu.tar.xz │x64 Linux │checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-aarch64-unknown-linux-musl.tar.xz │ARM64 MUSL Linux │checksum
─────────────────────────────────────────────────┼───────────────────┼─────────────
cargo-dist-x86_64-unknown-linux-musl.tar.xz │x64 MUSL Linux │checksum
─────────────────────────────────────────────────┴───────────────────┴─────────────
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo axodotdev/cargo-dist
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>