forked from crate-ci/escargot
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Cargo.toml
42 lines (37 loc) · 1.23 KB
/
Cargo.toml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
[package]
name = "escargot"
version = "0.5.2"
authors = ["Ed Page <eopage@gmail.com>"]
description = "Cargo API written in Paris"
license = "MIT OR Apache-2.0"
repository = "https://github.com/crate-ci/escargot.git"
homepage = "https://github.com/crate-ci/escargot"
documentation = "http://docs.rs/escargot/"
readme = "README.md"
categories = ["development-tools::build-utils"]
keywords = ["cargo", "packaging"]
edition = "2018"
[badges]
azure-devops = { project = "crate-ci", pipeline = "escargot" }
codecov = { repository = "crate-ci/escargot" }
maintenance = { status = "passively-maintained" }
[dependencies]
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
once_cell = "1.2.0"
log = "0.4"
[dev-dependencies]
assert_fs = "1.0"
[features]
# Upcoming features in cargo.
cargo_unstable = []
# Programmatic use of `cargo test` (relies on an unstable CLI API).
test_unstable = []
# This mostly exists for testing, to catch new fields and enum variants being
# added (for the cases we actually cover).
strict_unstable = []
# This is for when using `escargot` in tests and you want logged output to
# instead be printed because no logger is configured.
print = []
[package.metadata.docs.rs]
features = [ "cargo_unstable", "test_unstable" ]