shadi/release-plz.toml at main · agntcy/shadi · GitHub

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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
[workspace]
release_always = false
publish = true
# A library crate's artifact is the crates.io release; a GitHub release for it
# carries no assets. Only the two crates that ship binaries get one.
git_release_enable = false
publish_no_verify = true
publish_timeout = "30m"

[[package]]
name = "shadi_demo_bot"
publish = false
release = false

[[package]]
name = "agentbridge_demo"
publish = false
release = false

[[package]]
name = "shadi_desktop"
publish = false
release = false

[[package]]
name = "agntcy-shadi-cli"
git_release_enable = true
# The root CHANGELOG is the workspace-wide view, so release-plz owns it rather
# than anyone maintaining it by hand — the hand-written one had drifted twelve
# days and two releases behind. Paths are relative to the root Cargo.toml, so
# shadictl no longer keeps a crate-local changelog.
changelog_path = "CHANGELOG.md"
changelog_include = [
  "agntcy-agentbridge",
  "agntcy-agentbridge-cli",
  "agntcy-shadi-a2a",
  "agntcy-shadi-agent-secrets",
  "agntcy-shadi-agent-transport-slim",
  "agntcy-shadi-credential",
  "agntcy-shadi-identity",
  "agntcy-shadi-mas",
  "agntcy-shadi-memory",
  "agntcy-shadi-py",
  "agntcy-shadi-sandbox",
  "agntcy-shadi-slim-mas",
  "agntcy-shadi-telemetry",
]

[[package]]
name = "agntcy-agentbridge-cli"
git_release_enable = true

# cargo-semver-checks rebuilds each crate's crates.io baseline without a
# lockfile, and these baselines no longer build: a2a-client-lf 0.2.6 moved to
# a2a-lf 0.4, so a fresh resolve mixes A2A 0.3 and 0.4 types. Re-enable once a
# version of each built on the 0.4 SDK is published (agntcy/shadi#434).
[[package]]
name = "agntcy-agentbridge"
semver_check = false

[[package]]
name = "agntcy-shadi-a2a"
semver_check = false

[[package]]
name = "agntcy-shadi-mas"
semver_check = false