Small building blocks for the CI jobs we run again and again.
| Action | Use it when… | It does… |
|---|---|---|
setup-rust |
A job needs a pinned Rust toolchain or cross target. | Installs Rust components and targets, then caches the build. |
setup-proto-node-pnpm |
A repo pins Node and pnpm in .prototools. |
Installs both with proto and optionally caches the pnpm store. |
setup-pnpm-cache |
Node and pnpm are already installed. | Caches the pnpm store only. |
Use a reviewed, full commit SHA in each caller. A moving tag or branch can change code that runs in a job with release credentials without a change in the calling repo.
steps:
- uses: orin-dx/actions/setup-rust@<reviewed-full-commit-sha>
with:
toolchain: '1.96.0'
components: 'clippy,rustfmt'
targets: 'wasm32-wasip1'
- uses: orin-dx/actions/setup-proto-node-pnpm@<reviewed-full-commit-sha>
with:
working-directory: packages/my-node-packagesetup-proto-node-pnpm reads the calling repository's .prototools; it does not install Rust. Use setup-rust alongside it when the job also needs a specific Rust target.
See Contributing for validation and caller checks, or Security to report a credential or workflow issue privately. The main branch and current pinned SHAs receive fixes; callers choose when to move to a newer reviewed SHA.