Skip to content

fix(ci): pass the required toolchain input in the nightly relock Rust setup #1460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ErikBjare merged 1 commit into from
Sep 19, 2026
+5 −1
Merged

fix(ci): pass the required toolchain input in the nightly relock Rust setup #1460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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'
Expand Down
Loading