Files
Jens Nylander 9dbace4f4f release: ship sentio-mcp alongside sentio-smtp
The image now carries both binaries, so the release job lifts sentio-mcp
out of it the same way and no second set of release builds is needed.
Each gets its own archive: an MCP client host does not want the mail
server, and vice versa.

Notices are generated with --workspace now. Without it cargo-about
crawls only the root package, so rmcp and schemars would ship
unattributed.
2026-08-24 21:04:33 +02:00

39 lines
1.1 KiB
TOML

# cargo-about: which licences may appear in a distributed build, and where to
# find their texts. This is the attribution side; deny.toml is the policy side.
#
# cargo about generate --fail --workspace about.hbs > THIRD-PARTY-NOTICES.md
#
# `targets` is deliberately narrow. Without it the crawl includes crates that
# only build for other platforms - r-efi is a UEFI-only dependency, and pulling
# it in would attribute code no Linux build ever links.
accepted = [
"Apache-2.0",
"MIT",
"MIT-0",
"BSD-1-Clause",
"BSD-2-Clause",
"BSD-3-Clause",
"0BSD",
"ISC",
"Zlib",
"BSL-1.0",
"CC0-1.0",
"Unlicense",
"MPL-2.0",
"Unicode-3.0",
"Unicode-DFS-2016",
"CDLA-Permissive-2.0",
"OpenSSL",
]
targets = [
"x86_64-unknown-linux-gnu",
"aarch64-unknown-linux-gnu",
]
# Sentio's own crates are first-party; they have no business in a
# third-party notices file, and leaving them in means every version bump
# silently stales it.
private = { ignore = true }
ignore-build-dependencies = true
ignore-dev-dependencies = true