fix(release-plz): template compliant release PR title and body #121

Merged
jwilger merged 1 commit from fix/release-plz-pr-metadata into main 2026-06-13 19:52:37 -07:00
Owner

Summary

Template the release PR title and body that release-plz generates so they pass
the auto_review pre-merge metadata-quality gate without manual edits.

Rationale

auto_review rejected the last release PR (#120) three times for "PR metadata
quality": the default release title is just the version (no description) and the
body only restated it. Each release would otherwise require hand-editing the
title and body and re-triggering review. This sets:

  • pr_name: a conventional-commit title that adds a description after the
    version and stays under 72 characters ({{ version }} guarded for the
    multi-package case).
  • pr_body: a Summary + Rationale ("why") preamble followed by the per-package
    changelog, using release-plz's documented releases loop.

Verification

  • release-plz update loads the config without error (next version resolves;
    no TOML/schema error).
  • scripts/copyright-headers.sh --check and cargo fmt --all --check pass.
  • pr_name/pr_body Tera rendering will be exercised by the next release PR; the
    templates use only documented variables and the docs' releases loop syntax.

🤖 Generated with Claude Code

## Summary Template the release PR title and body that release-plz generates so they pass the `auto_review` pre-merge metadata-quality gate without manual edits. ## Rationale `auto_review` rejected the last release PR (#120) three times for "PR metadata quality": the default release title is just the version (no description) and the body only restated it. Each release would otherwise require hand-editing the title and body and re-triggering review. This sets: - `pr_name`: a conventional-commit title that adds a description after the version and stays under 72 characters (`{{ version }}` guarded for the multi-package case). - `pr_body`: a Summary + Rationale ("why") preamble followed by the per-package changelog, using release-plz's documented `releases` loop. ## Verification - `release-plz update` loads the config without error (next version resolves; no TOML/schema error). - `scripts/copyright-headers.sh --check` and `cargo fmt --all --check` pass. - pr_name/pr_body Tera rendering will be exercised by the next release PR; the templates use only documented variables and the docs' `releases` loop syntax. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(release-plz): template compliant PR title and body for releases
All checks were successful
CI / Nix flake check (pull_request) Successful in 2m46s
CI / Request auto_review semantic review (pull_request) Successful in 2s
auto_review auto_review: no findings
CI / Rust CI (pull_request) Successful in 9m21s
9b70710935
The auto_review pre-merge quality gate rejects release-plz's default release PR
metadata (title is just the version; body only restates it), forcing a manual
title/body edit on every release. Configure pr_name to a conventional title with
a description after the version (kept under 72 chars) and pr_body to lead with
Summary and Rationale before the per-package changelog, so release PRs pass the
gate automatically.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
auto-review left a comment

The PR updates the release-plz.toml configuration to template the release PR title and body, ensuring compliance with the auto_review metadata-quality gate. This change automates the process, reducing the need for manual edits and re-reviews.

Walkthrough

  • release-plz.toml:
    • The pr_name is updated to include a version and description, ensuring it adheres to conventional commit standards and stays under 72 characters.
    • The pr_body is templated to include a summary, rationale, and detailed changelog for each package, improving the clarity and completeness of release PRs.

LLM usage and cost

The PR updates the `release-plz.toml` configuration to template the release PR title and body, ensuring compliance with the `auto_review` metadata-quality gate. This change automates the process, reducing the need for manual edits and re-reviews. ## Walkthrough - **release-plz.toml**: - The `pr_name` is updated to include a version and description, ensuring it adheres to conventional commit standards and stays under 72 characters. - The `pr_body` is templated to include a summary, rationale, and detailed changelog for each package, improving the clarity and completeness of release PRs. ## LLM usage and cost - Reasoning (gpt-4o) in=1447 out=142 cost=$0.009365 - Cheap (gpt-4o-mini) in=553 out=47 cost=$0.000111 Estimated total USD: $0.009476 via https://api.openai.com and https://api.openai.com
jwilger deleted branch fix/release-plz-pr-metadata 2026-06-13 19:52:37 -07:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Slipstream/emc!121
No description provided.