kyle/tines
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

build(fuzz): require tines-core 1 and check the fuzz crate in ci.sh

Browse Source 
fuzz/Cargo.toml still required tines-core 0.3.0, so since the 1.0.0
version bump `cargo fuzz run node` failed version selection (B6). The
requirement is now "1" and the lock is regenerated.

scripts/ci.sh now runs rustfmt and clippy (all targets, -D warnings) on
the out-of-workspace fuzz crate on the pinned stable toolchain, so it
can't silently stop building again. fuzz/.gitignore ignores target,
artifacts and coverage.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
kyle
2026-10-22 08:44:09 -07:00
co-authored by Claude Opus 5.5
parent 13aaa5d5f7
commit e65a9dee6c
4 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/ci.sh
+5
View File
@@ -19,3 +19,8 @@ cargo test --locked -p tines-core --no-default-features
# no_std + conformance combination is actually exercised (not just by inspection).
cargo test --locked -p tines-core --no-default-features --features conformance
sh scripts/check-no-std.sh
# The fuzz crate sits outside the workspace and only *runs* on nightly
# (cargo-fuzz, see .github/workflows/fuzz.yml), but it must keep resolving and
# compiling on the pinned stable toolchain, or the scheduled job rots unseen.
cargo fmt --manifest-path fuzz/Cargo.toml -- --check
cargo clippy --locked --manifest-path fuzz/Cargo.toml --all-targets -- -D warnings