From 65d9c144f70de18543844f500a1963f1c000ef51 Mon Sep 17 00:00:00 2001 From: Georg Semmler Date: Mon, 15 Dec 2025 16:07:12 +0100 Subject: [PATCH] Exclude development scripts from published package During a dependency review we noticed that the unicode-segmentation crate includes various development scripts. These development scripts 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 | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Cargo.toml b/Cargo.toml index 1aac6ea..2a0fae8 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -16,7 +16,16 @@ This crate provides Grapheme Cluster, Word and Sentence boundaries according to Unicode Standard Annex #29 rules. """ -exclude = ["/.github", "/benches/texts", "/scripts/**.rs", "*.txt"] +include = [ + "COPYRIGHT", + "LICENSE-MIT", + "LICENSE-APACHE", + "Cargo.toml", + "src/**/*.rs", + "README.md", + "tests/**/*.rs", + "benches/**/*.rs", +] [features] no_std = [] # This is a no-op, preserved for backward compatibility only.