ci(release-plz): skip cascade feat(data) commits so no empty code releases

[polaz]

Problem

Data updates land via the off-tag PSL cascade (psl-cascade.yml): it cuts the data release, publishes, and writes its own CHANGELOG entry. But release-plz still sees the synced feat(data): bump PSL data ... commits on main as unreleased features and opens an empty code-release PR (version bump only, no changelog) — e.g. #67 chore: release v0.0.17 with zero changelog delta, duplicating already-published data.

Fix

Add a commit parser to .release-plz.toml that skips ^feat\(data\) (before the generic ^feat rule), so release-plz ignores cascade data commits and only opens release PRs for genuine code changes. Data releases remain fully handled by the cascade.

Acceptance

• After merge, release-plz recomputes and closes the empty release PR (chore: release v0.0.17 #67)
• A data-only cascade sync no longer produces a release-plz PR
• Genuine code changes still produce a release PR

Estimate

20m

[coderabbitai]

🔗 Related PRs

#29 - fix: add publish=false to release-plz config [closed]
#48 - feat(deps): migrate PSL to structured-public-domains + cascade releases [merged]
#62 - ci: make PSL cascade self-merge and carry the domain diff [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!