release-plz.toml

# release-plz configuration for katgpt-rs
#
# Only `katgpt-core` is released (published to crates.io). The root `katgpt-rs`
# crate is a dev/examples/aggregator playground — it is never published, so its
# version number carries no meaning for any downstream consumer.
#
# See README.md §"Releasing & Deploying" for the full dev→deploy workflow.

[[package]]
name = "katgpt-rs"
release = false  # never version-bump, never tag, never changelog
publish = false  # match Cargo.toml's publish = false (release-plz validates consistency)

[[package]]
name = "katgpt-core"
# Use package-prefixed tags to avoid collision with legacy root-crate tags
# (v0.1.0 "Community engine freeze", v0.2.0 "Release v0.2.0") that predate
# release-plz. Without this override, release-plz defaults to `v{{version}}`
# (because only one package is public), finds the legacy `v0.2.0` tag, assumes
# katgpt-core@0.2.0 was released, then bails with:
#   "package katgpt-core not found in the registry, but the git tag v0.2.0 exists"
# With this prefix, release-plz looks for `katgpt-core-v{{version}}` instead,
# which doesn't exist yet — so katgpt-core is treated as a fresh publish.
git_tag_name = "katgpt-core-v{{version}}"