You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f7b0031
Browse filesBrowse the repository at this point in the historyBrowse files
build(mise): move the cargo tools into mise.test.toml, pinned
mise merges config down the directory tree, so every tool in the root
mise.toml is also part of the toolset in packages/eql and in
languages/typescript/packages/protect-ffi. Their CI jobs run
`mise install` (and `mise run`) in those folders, so each one now built
cargo-nextest, cargo-llvm-cov, cargo-crap, cargo-mutants, cargo-fuzz and
cargo-udeps from source, none of which they use.
mise's cargo backend compiles a `cargo:` tool with the runner's default
rustc (1.92 on the Ubuntu images), not the root's pinned 1.94.1. So a
`latest` that raises its minimum Rust fails the install: cargo-udeps
0.1.61 needs cargo@0.96, which needs rustc 1.93. That broke the
protect-ffi integration suite on #1001 and the new udeps job on #1003.
The cargo tools move to mise.test.toml, which mise loads only for the
`test` environment (`mise x --env test`, or MISE_ENV=test). Nested
workspaces no longer inherit them. Each is pinned to an exact version
that builds on the runners' rustc; cargo-udeps goes back to 0.1.60.
The tasks that call them (crap:*, mutants:*, fuzz:*, and nextest in
wasm:guest:test and wasm:auth-guest:test) now run them through
`mise x --env test --`, as test:doc and the crap coverage step already
did, so `mise run <task>` keeps working locally without MISE_ENV.
Rust, Go, golangci-lint and wasm-pack stay in the root mise.toml. They
are prebuilt downloads, and plan section 3.5 has protect-ffi inherit
the Rust pin. That section's intent holds: the repository pins one
version of each cargo tool, reached through mise. The pins now sit in
the test environment rather than the default one.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PaY5xYydZUWhv8Nex9Sw8a
run = "cargo +nightly fuzz run access_key_parse --sanitizer none --target $(rustc -vV | sed -n 's/^host: //p') -- -max_total_time=60"
54
+
run = "mise x --env test -- cargo +nightly fuzz run access_key_parse --sanitizer none --target $(rustc -vV | sed -n 's/^host: //p') -- -max_total_time=60"
55
55
56
56
# Fuzz the JWT claims decode path (Token::fuzz_decode_claims, behind the `fuzz`
57
57
# feature). On native this is the jsonwebtoken-based decode with signature
58
58
# validation disabled. Same flags/rationale as fuzz:access-key.
run = "cargo +nightly fuzz run sealed_value_decode --sanitizer none --target $(rustc -vV | sed -n 's/^host: //p') -- -max_total_time=60"
33
+
run = "mise x --env test -- cargo +nightly fuzz run sealed_value_decode --sanitizer none --target $(rustc -vV | sed -n 's/^host: //p') -- -max_total_time=60"
34
34
35
35
# Fuzz the SEM index-term byte decoders — every `from_bytes` / `TryFrom<&[u8]>`
36
36
# a stored term comes back through (equality, match, ORE and OPE). One target
@@ -39,7 +39,7 @@ run = "cargo +nightly fuzz run sealed_value_decode --sanitizer none --target $(r
run = "cargo +nightly fuzz run client_key_encoded --sanitizer none --target $(rustc -vV | sed -n 's/^host: //p') -- -max_total_time=60"
14
+
run = "mise x --env test -- cargo +nightly fuzz run client_key_encoded --sanitizer none --target $(rustc -vV | sed -n 's/^host: //p') -- -max_total_time=60"
15
15
16
16
# Rustdoc with warnings as errors: a broken intra-doc link or a rustdoc
17
17
# warning fails the build. Doc *examples* are `test:doc:stack-kms`. Both run
0 commit comments