Cargo.toml

[workspace]
resolver = "3"
members = ["krit-core", "krit", "krit-tui"]

[workspace.package]
version = "0.12.3"
edition = "2024"
license = "MIT"

[workspace.dependencies]
krit-core = { path = "krit-core" }
serde = { version = "1", features = ["derive"] }
serde_json = "1"
# No default features: those are rustls and gzip, and every request krit's
# clients make is plaintext HTTP to a loopback server they usually started
# themselves.
#
# Nothing degrades to plaintext silently — an https:// URI fails with
# `Error::TlsRequired` rather than being retried in the clear. But it fails as
# an ordinary transport error, not loudly: a call site that discards errors
# (`client::probe`) reads it as "no server there", which is why `ApiError`
# names the scheme rather than leaving the generic "did krit crash?".
# A client that grows a remote endpoint has to add the feature back.
ureq = { version = "3", default-features = false, features = ["json"] }

# Profiles are only honored at the workspace root — cargo silently ignores a
# member's `[profile]`, so this must live here rather than in krit/.
[profile.release]
lto = true
strip = true