Skip to content

Commit

Permalink
ci: use cargo binstall in release workflow
Browse files Browse the repository at this point in the history
This change was applied to the testing workflow but not the main release workflow. Aligning the two
now.
  • Loading branch information
jacderida committed Jul 2, 2024
1 parent 0200e71 commit 998de43
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 3 deletions.
3 changes: 2 additions & 1 deletion .github/workflows/build-release-artifacts.yml
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,8 @@ jobs:
with:
ref: ${{ inputs.branch }}
- uses: dtolnay/rust-toolchain@stable
# cargo-binstall will try and use pre-built binaries if they are available (also speeds up installing `cross`)
# cargo-binstall will try and use pre-built binaries if they are available and also speeds up
# installing `cross`
- uses: cargo-bins/cargo-binstall@main
- shell: bash
run: cargo binstall --no-confirm just
Expand Down
6 changes: 4 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,9 +59,11 @@ jobs:
steps:
- uses: actions/checkout@v4
- uses: dtolnay/rust-toolchain@stable
# It's quite slow to install just by building it, but here we need a cross-platform solution.
# cargo-binstall will try and use pre-built binaries if they are available and also speeds up
# installing `cross`
- uses: cargo-bins/cargo-binstall@main
- shell: bash
run: cargo install just
run: cargo binstall --no-confirm just

# Set the network versioning based on our branch or workflow input
- name: provide network versioning
Expand Down

0 comments on commit 998de43

Please sign in to comment.