Skip to content

Use explicit Rust targets and reuse installed Cargo tools - #150

Open
timkpaine wants to merge 2 commits into
mainfrom
tkp/use-explicit-rust-setup
Open

timkpaine wants to merge 2 commits into
mainfrom
tkp/use-explicit-rust-setup

Conversation

@timkpaine

@timkpaine timkpaine commented Jul 21, 2026 •

Copy link
Copy Markdown
Member

Use the narrowed Rust setup from actions-ext/rust#5 at 3b918cc2cb4a231ad3752f8cc129da5f07626ce2 in repository CI and both Rust templates. Native builds use the host target; Rust/WASM explicitly requests wasm32-unknown-unknown.

Keep Cargo tool installation in generated Makefiles and remove forced reinstalls, including the optional JS setup command. Cargo checks installed versions directly, and the wasm-bindgen CLI keeps its existing exact version matching the WASM crate. Resolve conflicts against current main and the template directory move.

Rendered and actionlint-validated both variants for Python 3.10–3.13 with Pyodide enabled and disabled (16 configurations). Both generated requirement targets reuse cached tools without compilation in an isolated install directory, and generated Rust library tests pass. git diff --check passes.

Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
@timkpaine timkpaine changed the title Use explicit Rust setup inputs Use explicit Rust targets and reuse installed Cargo tools Oct 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant