Setup a specific Rust toolchain with extra features like problem matchers
Go to file
Jonas Bushart 4d1965c914 Add override input parameter that controls the `rustup override` behavior 2024-09-22 16:04:02 +02:00
.github chore: prepare release 1.8.0 2024-01-13 17:45:49 +00:00
test-workspace ci: add cache-workspaces test 2024-01-13 17:25:41 +00:00
.pre-commit-config.yaml Add pre-commit for basic checks 2024-09-20 00:46:09 +02:00
CHANGELOG.md Add override input parameter that controls the `rustup override` behavior 2024-09-22 16:04:02 +02:00
LICENSE Initial commit 2022-04-17 21:06:51 +02:00
README.md Add override input parameter that controls the `rustup override` behavior 2024-09-22 16:04:02 +02:00
action.yml Add override input parameter that controls the `rustup override` behavior 2024-09-22 16:04:02 +02:00
rust.json Add new problem matcher that is aware of color codes 2023-03-18 00:18:20 +01:00

README.md

Install Rust Toolchain

This GitHub Action installs a Rust toolchain using rustup. It further integrates into the ecosystem. Caching for Rust tools and build artifacts is enabled. Environment variables are set to optimize the cache hits. Problem Matchers are provided for build messages (cargo, clippy) and formatting (rustfmt).

The action is heavily inspired by dtolnay's https://github.com/dtolnay/rust-toolchain and extends it with further features.

Example workflow

name: "Test Suite"
on:
  push:
  pull_request:

jobs:
  test:
    name: cargo test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions-rust-lang/setup-rust-toolchain@v1
      - run: cargo test --all-features

  # Check formatting with rustfmt
  formatting:
    name: cargo fmt
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      # Ensure rustfmt is installed and setup problem matcher
      - uses: actions-rust-lang/setup-rust-toolchain@v1
        with:
          components: rustfmt
      - name: Rustfmt Check
        uses: actions-rust-lang/rustfmt@v1

Inputs

All inputs are optional. If a toolchain file (i.e., rust-toolchain or rust-toolchain.toml) is found in the root of the repository and no toolchain value is provided, all items specified in the toolchain file will be installed. If a toolchain value is provided, the toolchain file will be ignored. If no toolchain value or toolchain file is present, it will default to stable. First, all items specified in the toolchain file are installed. Afterward, the components and target specified via inputs are installed in addition to the items from the toolchain file.

Name Description Default
toolchain Comma-separated list of Rustup toolchain specifier e.g. stable, nightly, 1.42.0. The last version is the default. stable
target Additional target support to install e.g. wasm32-unknown-unknown
components Comma-separated string of additional components to install e.g. clippy, rustfmt
cache Automatically configure Rust cache (using Swatinem/rust-cache) true
cache-directories Propagates the value to Swatinem/rust-cache
cache-workspaces Propagates the value to Swatinem/rust-cache
cache-on-failure Propagates the value to Swatinem/rust-cache true
cache-key Propagates the value to Swatinem/rust-cache as key
matcher Enable problem matcher to surface build messages and formatting issues true
rustflags Set the value of RUSTFLAGS (set to empty string to avoid overwriting existing flags) "-D warnings"
override Setup the last installed toolchain as the default via rustup override true

RUSTFLAGS

By default, this action sets the RUSTFLAGS environment variable to -D warnings. However, rustflags sources are mutually exclusive, so setting this environment variable omits any configuration through target.*.rustflags or build.rustflags.

  • If RUSTFLAGS is already set, no modifications of the variable are made and the original value remains.
  • If RUSTFLAGS is unset and the rustflags input is empty (i.e., the empty string), then it will remain unset. Use this, if you want to prevent the value from being set because you make use of target.*.rustflags or build.rustflags.
  • Otherwise, the environment variable RUSTFLAGS is set to the content of rustflags.

To prevent this from happening, set the rustflags input to an empty string, which will prevent the action from setting RUSTFLAGS at all, keeping any existing preferences.

You can read more rustflags, and their load order, in the Cargo reference.

Outputs

Name Description
rustc-version Version as reported by rustc --version
cargo-version Version as reported by cargo --version
rustup-version Version as reported by rustup --version
cachekey A short hash of the installed rustc version

License

The scripts and documentation in this project are released under the MIT License.