ci: temporarily disable release-plz crates.io publish

[getappz]

Summary

• ponytail was published to crates.io then deleted (an account owner used crates.io's delete-recently-published feature). The name is in a ~24h reuse cooldown until 2026-07-09T08:42:28Z. agentflare depends on ponytail via a path dependency, so it can't publish to crates.io either until the cooldown clears.
• Set publish = false at the workspace level in release-plz.toml so release-plz still version-bumps, changelogs, tags, and pushes — unblocking the v1.2.0 git tag and the downstream binary release (release.yml → GitHub Release + binstall assets) without waiting on crates.io.
• Deleted the ponytail-v0.1.0 and agent-registry-v0.1.0 git tags (both remote-only, force-pushed off). Neither corresponds to an actually-published crate anymore (ponytail was deleted from the registry; agent-registry was renamed to agentflare-agent-registry in fix: scope internal crate names, pin path-dep versions for crates.io publish #100), and release-plz's version-diff step was refusing to run because of that exact "tag exists but crate not found in registry" inconsistency.

Follow-up

Once the cooldown clears (2026-07-09T08:42:28Z), remove the publish = false line (or flip to true) to resume normal crates.io publishing for ponytail, agentflare-agent-registry, agentflare-skill-registry, and agentflare.

Test plan

• TOML syntax valid
• After merge, re-run release-plz and confirm it now produces a release PR / tags without hitting the crates.io lookup error

Summary by CodeRabbit

• Chores
  • Temporarily disabled workspace publishing to prevent release issues until a package name cooldown period expires.
  • Added a note clarifying when publishing can be re-enabled.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release-plz.toml configuration file is updated to disable workspace-wide crate publishing by setting publish = false, accompanied by a comment documenting a temporary crates.io name cooldown for the ponytail crate.

Changes

Release Config Update

Layer / File(s)	Summary
Disable publishing in release-plz.toml release-plz.toml	Sets publish = false at the workspace level and adds a comment noting a temporary crates.io name cooldown for ponytail.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: temporarily disabling release-plz crates.io publishing.
Description check	✅ Passed	The description covers Summary and Test plan well; the Notes for reviewers section is missing, but that is a non-critical omission.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/disable-crates-publish-temporarily

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

release-plz.toml (1)

4-10: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

LGTM — valid, well-documented temporary workaround.

publish is a legitimate [workspace]-level release-plz field, and the comment clearly documents the cooldown window and revert steps.

One suggestion: since this relies on someone remembering to revert it, consider filing a tracking issue (or a dated calendar reminder) referencing this change, so it isn't left disabled beyond the cooldown window if the comment is missed during a future refactor.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@release-plz.toml` around lines 4 - 10, The temporary workspace-wide publish
disablement needs a durable reminder so it is not forgotten after the cooldown
window. Update the `release-plz.toml` `publish = false` block to reference a
tracking issue or reminder ID in the existing temporary workaround comment, and
make sure the note clearly points back to this `publish` setting so it can be
reverted when the cooldown expires.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@release-plz.toml`:
- Around line 4-10: The temporary workspace-wide publish disablement needs a
durable reminder so it is not forgotten after the cooldown window. Update the
`release-plz.toml` `publish = false` block to reference a tracking issue or
reminder ID in the existing temporary workaround comment, and make sure the note
clearly points back to this `publish` setting so it can be reverted when the
cooldown expires.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 12869134-a7f4-421b-9ed5-5686d1233f78

📥 Commits

Reviewing files that changed from the base of the PR and between 91dcebb and 209bd09.

📒 Files selected for processing (1)

• release-plz.toml