diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 6094f51..f93ae50 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -93,7 +93,7 @@ jobs: name: coverage-report path: coverage/ - name: Generate badge - uses: jaywcjlove/coverage-badges-cli@v2.2.0 + uses: jaywcjlove/coverage-badges-cli@v2.3.0 with: source: coverage/coverage-summary.json output: coverage/badge.svg diff --git a/.github/workflows/dart-bindings.yml b/.github/workflows/dart-bindings.yml index 6140bea..86a4345 100644 --- a/.github/workflows/dart-bindings.yml +++ b/.github/workflows/dart-bindings.yml @@ -34,7 +34,7 @@ jobs: # Pinned to match python-bindings.yml, same reasoning: a floating # toolchain turns an unrelated Rust release into a red gate on an # untouched branch. - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 with: components: rustfmt, clippy @@ -79,7 +79,7 @@ jobs: steps: - uses: actions/checkout@v4 - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 - uses: Swatinem/rust-cache@v2 with: @@ -106,7 +106,7 @@ jobs: steps: - uses: actions/checkout@v4 - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 - uses: Swatinem/rust-cache@v2 with: diff --git a/.github/workflows/parity.yml b/.github/workflows/parity.yml index 45adf02..e099560 100644 --- a/.github/workflows/parity.yml +++ b/.github/workflows/parity.yml @@ -33,7 +33,7 @@ jobs: # Must stay equal to `crates/rust-toolchain.toml`, for the same reason the # Rust workflow pins it: rustup reads that file inside `crates/`, so a # disagreement here installs one toolchain and builds with another. - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 - uses: Swatinem/rust-cache@v2 with: diff --git a/.github/workflows/python-bindings.yml b/.github/workflows/python-bindings.yml index 147b5b9..5304413 100644 --- a/.github/workflows/python-bindings.yml +++ b/.github/workflows/python-bindings.yml @@ -35,7 +35,7 @@ jobs: # Pinned to match crates/rust-toolchain.toml, same reasoning as rust.yml: # a floating toolchain turns an unrelated Rust release into a red gate on # an untouched branch. - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 with: components: rustfmt, clippy @@ -77,7 +77,7 @@ jobs: steps: - uses: actions/checkout@v4 - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 - uses: actions/setup-python@v5 with: @@ -104,7 +104,7 @@ jobs: steps: - uses: actions/checkout@v4 - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 - uses: actions/setup-python@v5 with: diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml index dcf39cf..37264f3 100644 --- a/.github/workflows/rust.yml +++ b/.github/workflows/rust.yml @@ -36,7 +36,7 @@ jobs: # an untouched branch. This must stay equal to `crates/rust-toolchain.toml` # — rustup reads that file inside `crates/`, so a disagreement here means # the runner installs one toolchain and cargo silently fetches another. - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 with: components: rustfmt, clippy diff --git a/.github/workflows/wasm-bindings.yml b/.github/workflows/wasm-bindings.yml index a52f76a..9128ab2 100644 --- a/.github/workflows/wasm-bindings.yml +++ b/.github/workflows/wasm-bindings.yml @@ -42,7 +42,7 @@ jobs: # patch, and the committed core-harness.js/.d.ts (deterministic; see the # drift check below) have to byte-match a build made with this exact # toolchain. - - uses: dtolnay/rust-toolchain@1.97.1 + - uses: dtolnay/rust-toolchain@1.100.0 with: targets: wasm32-unknown-unknown