max / pter

Gate the crates.io publish on clippy and tests The publish recipe's prebuild step now runs clippy -D warnings alongside the test suite it already ran. A published version can be yanked but never edited, so this is the last point at which a break is still cheap. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-07-22 04:18 UTC

Commit: f59ac844ea4e427082d0ec72202dbad505ed4d6a

Parent: 04348b0

1 file changed, +6 insertions, -2 deletions

M dist/recipes/publish.rhai +6 -2

			@@ -16,8 +16,12 @@ let v = version();
16	16		step("checkout");
17	17		sh_ok(h, "cd " + r + " && git pull --ff-only");
18	18
19		-	step("build");
20		-	sh_ok(h, "cd " + r + " && cargo test " + feature_flags());
	19	+	// Gate: nothing reaches crates.io from code that fails clippy or its tests. A
	20	+	// published version can be yanked but never edited, so this is the last point
	21	+	// at which a break is still cheap.
	22	+	step("prebuild");
	23	+	sh_ok(h, "cd " + r + " && cargo clippy --workspace --all-targets " + feature_flags() + " -- -D warnings");
	24	+	sh_ok(h, "cd " + r + " && cargo test --workspace " + feature_flags());
21	25
22	26		step("verify");
23	27		// Credentials are checked here too, and deliberately not passed through Bento: