From 38c0f8d46712ad32aaa5d5246dfb19519bb79c98 Mon Sep 17 00:00:00 2001 From: Bob Date: Sat, 19 Sep 2026 04:19:38 +0000 Subject: [PATCH] fix(ci): pass the required toolchain input in the nightly relock Rust setup The 'Set up Rust for the nightly relock' step used dtolnay/rust-toolchain without its required 'toolchain' input, so every nightly run failed at that step with "'toolchain' is a required input" and the whole Build Tauri artifacts job was skipped. Install stable there like the other Rust steps do; re-installing an already-present toolchain is a no-op. Git-Session-Id: 53fa68e9-eeea-5397-82f3-b0d9dc10bd6a --- .github/workflows/release.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index d8f82be00..507e369dd 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1237,10 +1237,14 @@ jobs: # On a nightly the aw-server-rust submodule has moved but aw-tauri's # Cargo.lock still pins the old revision; relock it so Tauri really builds # the latest server and the verification below still holds. Needs cargo, - # which this job only installs later — the toolchain action is idempotent. + # which this job only installs later, so install stable here too. The + # `toolchain` input is required by dtolnay/rust-toolchain; re-installing a + # toolchain that is already present is a no-op. - name: Set up Rust for the nightly relock if: needs.nightly-submodules.outputs.latest == 'true' uses: dtolnay/rust-toolchain@3c5f7ea28cd621ae0bf5283f0e981fb97b8a7af9 # master + with: + toolchain: stable - name: Relock aw-tauri Cargo.lock to the latest aw-server-rust (nightly) if: needs.nightly-submodules.outputs.latest == 'true'