Files
ironclaw/release-plz.toml
Henry Park be6de43f8e fix(ci): unblock v0.25.0 release — fix tag filter and publish config (#2306)
The release pipeline broke when ironclaw_engine was added (Apr 2) with
a monty git dependency that blocks crates.io publishing. Additionally,
sub-crate tags (ironclaw_tui-v0.1.0) were triggering cargo-dist builds
and stealing the "Latest" badge from the main release.

- Narrow release.yml tag pattern to `ironclaw-v*` so only the main
  binary release tags trigger cargo-dist (not sub-crate tags)
- Configure release-plz to skip crates.io publish for ironclaw
  (publish = false) while still creating git tags for cargo-dist
- Mark ironclaw_engine, ironclaw_tui, ironclaw_gateway as
  non-publishable (release = false) in release-plz.toml
- Add publish = false to tui and gateway Cargo.toml
- Remove version fields from non-publishable path deps in root
  Cargo.toml

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-10 17:59:51 -07:00

29 lines
880 B
TOML

[workspace]
# GitHub Releases are created by cargo-dist (release.yml), not release-plz.
# release-plz only creates git tags and publishes to crates.io.
git_release_enable = false
# ── Main binary ─────────────────────────────────────────────
# Cannot publish to crates.io because ironclaw_engine depends on `monty`
# (git-only, not on crates.io). Still create git tags so cargo-dist builds
# binaries and creates GitHub Releases.
[[package]]
name = "ironclaw"
publish = false
# ── Internal crates (not useful standalone) ─────────────────
[[package]]
name = "ironclaw_engine"
publish = false
release = false
[[package]]
name = "ironclaw_tui"
publish = false
release = false
[[package]]
name = "ironclaw_gateway"
publish = false
release = false