From 9cb1712c199b6c61a42b9e0fbca283c5e73aa4e8 Mon Sep 17 00:00:00 2001 From: Georg Semmler Date: Mon, 15 Dec 2025 16:15:45 +0100 Subject: [PATCH] Exclude development scripts from the published package During a dependency review we noticed that the target-lexicon crate includes a development script. This development script shouldn't be there as they might, at some point become problematic. As of now they prevent any downstream user from enabling the `[bans.build.interpreted]` option of cargo deny. I opted for using an explicit include list instead of an exclude list to prevent these files from beeing included in the published packages to make sure that everything that's included is an conscious choice. --- Cargo.toml | 1 + 1 file changed, 1 insertion(+) diff --git a/Cargo.toml b/Cargo.toml index 204062e..ed5afb1 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -10,6 +10,7 @@ categories = ["no-std"] license = "Apache-2.0 WITH LLVM-exception" repository = "https://github.com/bytecodealliance/target-lexicon" edition = "2018" +include = ["Cargo.toml", "README.md", "LICENSE", "build.rs", "src/**/*.rs"] [dependencies] serde = { version = "1.0", optional = true }