chore: label release PRs with release

[jdx]

https://entire.io/gh/jdx/demand/trails/24

Release PRs opened by release-plz now carry the release label, so they can be found and filtered the same way as in hk, usage and mise.

[workspace]
pr_labels = ["release"]

release-plz also adds any missing configured labels when it updates an already-open release PR, so the current one picks the label up on the next run after this merges.

AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: claude-code_2-1-289_agent.

🤖 Generated with Claude Code

---

Note

Low Risk
Release automation config only; no runtime or application behavior changes.

Overview
Configures release-plz to tag automated release pull requests with the release label via pr_labels = ["release"] in release-plz.toml, matching how release PRs are labeled in other repos (e.g. hk, usage, mise) so they are easier to find and filter.

A short comment documents the intent. After merge, release-plz will also apply the label when it updates an already-open release PR.

^{Reviewed by Cursor Bugbot for commit 861f38f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Summary by CodeRabbit

• Chores
  • Release pull requests are now labeled release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Central YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4b08d426-cac3-44cb-a297-fa801782a663

📥 Commits

Reviewing files that changed from the base of the PR and between d30e03a and 861f38f.

📒 Files selected for processing (1)

• release-plz.toml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

---

📝 Walkthrough

Walkthrough

The release configuration now assigns the release label to release pull requests. A comment describes the label’s intended use.

Changes

Release pull request labeling

Layer / File(s)	Summary
Configure release label release-plz.toml	The configuration assigns the release label to release pull requests. A comment describes the label’s intended use.

Priority: ⬇️ Low

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

Change: Feature

Merge Risk: ⚪ Minimal · up to 861f3

Release PRs can receive the configured label, including already-open PRs. No merge-blocking risk is established.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: applying the release label to release pull requests.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Confidence Score: 5/5

[Low risk] Adds a label to automated release pull requests.

This PR appears safe to merge.

Summary

Adds pr_labels = ["release"] under [workspace] in release-plz.toml so release PRs carry the release label.

• No actionable issues found.

_{Reviews (1) · Last reviewed commit: "chore: label release PRs with release" · Reviewed by Greptile}