fix(release-notes): filter stale release PRs

[chenjiahan]

GitHub-generated release notes can include the previous version's release PR when that PR merges after its tag. This updates the draft release note skill to remove clearly stale release PR entries while preserving current-version and ambiguous items. Removed entries are reported verbatim to the user outside the release note body.

[coderabbitai]

Warning

Review limit reached

@chenjiahan, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a677ff20-8d10-49cc-ac21-cfece62f9d7e

📥 Commits

Reviewing files that changed from the base of the PR and between 29d0810 and ddf3463.

📒 Files selected for processing (1)

• .agents/skills/create-draft-release-notes/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chenjiahan/fix-stale-release-pr-notes

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ddf3463b94

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Require tag context before filtering Markdown-only notes

When the Markdown-Only workflow is used, neither release_tag nor previous_tag is collected, so the supplied Markdown alone cannot establish whether a bullet such as release: v1.0.0 is stale or is the release currently being prepared. Applying this global removal rule to that workflow can therefore silently delete a valid current-release PR; limit filtering to workflows with a known release range, or require the tag/range as Markdown-Only input.

Useful? React with 👍 / 👎.