mlua-swarm 0.8.0

Swarm engine host built on mlua — long-running stateful runtime with Role/Verb gate, CapToken, 3-stage pipeline, and Middleware overlay.
Documentation
[workspace]
changelog_update = false     # default off; only the root crate updates the root CHANGELOG
dependencies_update = false
git_release_enable = false   # GitHub Release is created by cargo-dist
git_tag_enable = false       # default off; only the representative crate tags
git_tag_name = "v{{ version }}"  # unified tag name, also used for CHANGELOG compare links
semver_check = true
release_always = false       # publish only when the release PR is merged
pr_labels = ["release"]

# Keep all 4 crates in lockstep versioning.
# Only the root crate maintains the (root) CHANGELOG.md.
[[package]]
name = "mlua-swarm"
version_group = "mse"
changelog_update = true
# release-plz assigns each commit to the crate whose path it touches;
# a commit that only touches `crates/*/…` never lands in the root
# crate's CHANGELOG. Since the whole workspace ships lockstep under
# `version_group = "mse"`, tell release-plz to fold every sibling
# crate's commits into the single unified root CHANGELOG. Without
# this, feat/fix commits scoped to a sibling crate disappear from
# every CHANGELOG (see v0.4.0 — only the one commit that touched
# `src/` made it in; the other four were dropped).
changelog_include = ["mlua-swarm-schema", "mlua-swarm-server", "mlua-swarm-cli"]

[[package]]
name = "mlua-swarm-schema"
version_group = "mse"

[[package]]
name = "mlua-swarm-server"
version_group = "mse"

# Representative crate: creates the single unified tag v{version},
# which is what the cargo-dist + MCP Registry workflow (release.yml) keys on.
[[package]]
name = "mlua-swarm-cli"
version_group = "mse"
git_tag_enable = true