🏁 Script executed:

#!/bin/bash
# Read-only verification:
# 1) Find non-SHA GitHub Action refs.
# 2) Resolve dtolnay/rust-toolchain tag commit SHA for 1.91.1.

set -euo pipefail

echo "== Non-SHA action refs in workflows/actions =="
rg -n --glob '.github/**' 'uses:\s+[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+@([^\s#]+)' | \
  rg -n -v '@[0-9a-fA-F]{40}\b' || true

echo
echo "== Resolve tag -> commit SHA for dtolnay/rust-toolchain@1.91.1 =="
gh api repos/dtolnay/rust-toolchain/git/ref/tags/1.91.1 | jq -r '.object.sha, .object.type'

Repository: OpenZeppelin/openzeppelin-relayer

Length of output: 393

🏁 Script executed:

#!/bin/bash
# Step 1: Explore .github directory structure
echo "=== .github directory structure ==="
find .github -type f -name "*.yml" -o -name "*.yaml" 2>/dev/null | head -20

echo
echo "=== Check if .github/actions/prepare/action.yml exists ==="
if [ -f ".github/actions/prepare/action.yml" ]; then
  echo "File exists. Content at lines 17-19:"
  sed -n '15,21p' ".github/actions/prepare/action.yml" | cat -n
else
  echo "File does not exist"
fi

echo
echo "=== All GitHub Actions uses statements ==="
rg 'uses:' '.github/' --no-heading || echo "(no matches found)"

Repository: OpenZeppelin/openzeppelin-relayer

Length of output: 13951

🌐 Web query:

dtolnay/rust-toolchain repository tag v1.91.1 commit SHA

💡 Result:

For the repository dtolnay/rust-toolchain, the tag v1.91.1 corresponds to the commit SHA f7ccc83f9ed1e5b9c81d8a67d7ad1a747e22a561.[1]

Citations:

• 1: dtolnay/rust-toolchain@f7ccc83...efa25f7

🌐 Web query:

dtolnay/rust-toolchain action inputs parameters documentation

💡 Result:

The dtolnay/rust-toolchain GitHub Action supports these input parameters (“with:” fields) and outputs: Inputs (with/): 1) toolchain (required: false) - Rustup toolchain specification string such as stable, nightly, 1.89.0, nightly-2025-01-01.[1][2] - The default behavior (if you do not set the input) is to match the action’s @rev (e.g., dtolnay/rust-toolchain@nightly pulls nightly; dtolnay/rust-toolchain@1.89.0 pulls 1.89.0).[1][2] - Note from the README: if you pass an explicit toolchain input instead of using the action @rev, use dtolnay/rust-toolchain@master as the revision of the action.[1] 2) targets (required: false) - Comma-separated list of Rust target triples to install for the chosen toolchain.[3][1] 3) target (required: false) - Alias for targets (same meaning: installs the listed target triples).[3] 4) components (required: false) - Comma-separated list of additional Rust components to install (examples given: clippy, rustfmt).[3][1] Outputs: 1) cachekey - A short hash of the installed rustc version, suitable for use as a cache key.[3][1] 2) name - Rustup’s selected toolchain name (example format like “1.62.0”), suitable for using with cargo +${{ steps..outputs.name }}.[3][1] Example usage: - uses: dtolnay/rust-toolchain@stable with: toolchain: nightly targets: wasm32-unknown-unknown components: clippy,rustfmt Grounding: the action.yml defines inputs toolchain, targets, target (alias), components, plus outputs cachekey and name.[3] The README documents the same inputs/outputs and explains the default behavior tied to the action @rev and the @master guidance when providing toolchain explicitly.[1][2]

Citations:

• 1: https://github.com/dtolnay/rust-toolchain/blob/master/README.md
• 2: https://github.com/dtolnay/rust-toolchain
• 3: https://github.com/dtolnay/rust-toolchain/blob/master/action.yml

🏁 Script executed:

#!/bin/bash
# Check the .github/actions/oidc/action.yml to see similar aws-actions pattern
echo "=== Reference: aws-actions/configure-aws-credentials usage ==="
rg -A 3 'uses: aws-actions/configure-aws-credentials' .github/ --no-heading || true

echo
echo "=== Check how prepare action uses the rust-toolchain action ==="
cat -n .github/actions/prepare/action.yml | head -30

Repository: OpenZeppelin/openzeppelin-relayer

Length of output: 1885

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.