From fc5c0a98c7f19acb9ccada14cd6a63d4c85e9b62 Mon Sep 17 00:00:00 2001 From: Philipp Schuster Date: Sat, 24 Aug 2024 17:10:35 +0200 Subject: [PATCH] ci: check if crate can be packaged This way, we can early spot issues before they occur in unfortunate situations, as happened with [0]. [0] https://github.com/rust-osdev/uefi-rs/pull/1338 --- .github/workflows/rust.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml index dfb4abe74..7ef8da0cc 100644 --- a/.github/workflows/rust.yml +++ b/.github/workflows/rust.yml @@ -121,6 +121,17 @@ jobs: # library packages. Note that xtask isn't used or built here; since it's # just a dev tool we don't care about the MSRV for that package. run: cargo build --target x86_64-unknown-uefi -p uefi-test-runner + # Tests that the published crates keep being package-able (thus, releasable). + package: + name: Package Crates + runs-on: ubuntu-latest + steps: + - name: Checkout sources + uses: actions/checkout@v4 + - uses: Swatinem/rust-cache@v2 + - name: Build + run: cargo package -p uefi -p uefi-raw -p uefi-macros + # This job requires the nightly channel, but keep it as a separate job from # `nightly_channel` because it takes a while to run. build_feature_permutations: