From 4f582616346b5ee5cebb034190183c2c935d29c2 Mon Sep 17 00:00:00 2001 From: Yasunobu <42543015+P4suta@users.noreply.github.com> Date: Tue, 4 Aug 2026 20:18:28 +0900 Subject: [PATCH] fix: keep xtask out of the release-plz publish set release-plz refused to run: ERROR Package `xtask` has `publish = false` or `publish = []` in the Cargo.toml, but it has `publish = true` in the release-plz configuration. `release = false` on the xtask package entry stops release-plz from releasing it, but the workspace-level `publish = true` still reaches it, and release-plz treats that disagreement with the manifest as a configuration error rather than ignoring it. Restate `publish = false` on the package entry. restart-manager does not hit this because its whole workspace is `publish = false`; conpty-oxide has no second workspace member at all. This is the first repository here that both publishes through release-plz and carries an xtask. Verified with `release-plz release --dry-run` locally: the configuration now parses and validates, leaving only the expected "git release not configured" error from having no token outside CI. Co-Authored-By: Claude Fable 5 --- release-plz.toml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/release-plz.toml b/release-plz.toml index db95f82..ea2578b 100644 --- a/release-plz.toml +++ b/release-plz.toml @@ -23,6 +23,11 @@ semver_check = true [[package]] name = "xtask" release = false +# `release = false` stops release-plz from releasing xtask, but the workspace +# `publish = true` above still reaches it, and release-plz rejects a package +# whose Cargo.toml says `publish = false` while its configuration says +# otherwise. Restate it here. +publish = false [changelog] protect_breaking_commits = true