Skip to content

Comments

Add .github/release.yml for auto-generated release notes#898

Merged
AyodeAwe merged 1 commit intoNVIDIA:mainfrom
AyodeAwe:add-release-yml
Feb 23, 2026
Merged

Add .github/release.yml for auto-generated release notes#898
AyodeAwe merged 1 commit intoNVIDIA:mainfrom
AyodeAwe:add-release-yml

Conversation

@AyodeAwe
Copy link
Collaborator

@AyodeAwe AyodeAwe commented Feb 23, 2026

Adds .github/release.yml to configure GitHub's auto-generated release notes with:

  • Label-based categorization: Breaking Changes, Bug Fixes, Documentation, New Features, Improvements
  • Bot exclusions: rapids-bot[bot], dependabot[bot]
  • Label exclusions: ignore-for-release, dependencies

This matches the standard configuration used across rapidsai repos (e.g., rmm).

Summary by CodeRabbit

  • Chores
    • Updated release automation configuration to improve changelog organization and filtering for future releases.

@AyodeAwe AyodeAwe requested a review from a team as a code owner February 23, 2026 17:37
@AyodeAwe AyodeAwe added non-breaking Introduces a non-breaking change improvement Improves an existing functionality labels Feb 23, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 23, 2026

📝 Walkthrough

Walkthrough

Adds a changelog configuration to .github/release.yml with exclude filters for labels and authors, and category mappings for organizing release notes into Breaking Changes, Bug Fixes, Documentation, New Features, and Improvements.

Changes

Cohort / File(s) Summary
Changelog Configuration
.github/release.yml
Added exclude filters for labels and authors, plus category mappings with emoji labels for organizing release notes (Breaking Changes, Bug Fixes, Documentation, New Features, Improvements).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately and concisely describes the main change: adding a .github/release.yml file for configuring auto-generated release notes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
.github/release.yml (1)

9-24: Consider adding a catch-all category for unlabelled PRs.

GitHub's release.yml supports * as a catch-all for pull requests that didn't match any of the previous categories. Without it, any PR that doesn't carry one of the five defined labels (breaking, bug, doc, feature request, improvement) — and isn't excluded — simply disappears from the generated release notes entirely rather than appearing in an "Other Changes" bucket.

💡 Proposed addition of a catch-all category
     - title: "🛠️ Improvements"
       labels:
         - improvement
+    - title: "🔄 Other Changes"
+      labels:
+        - "*"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/release.yml around lines 9 - 24, The categories list is missing a
catch-all so unlabelled PRs are omitted; add a final category entry to the
categories array (e.g., title "Other Changes") that uses the special catch-all
label '*' so any PR that didn't match the existing label sets (the current
category titles: "\U0001F6A8 Breaking Changes", "\U0001F41B Bug Fixes",
"\U0001F4D6 Documentation", "\U0001F680 New Features", "\U0001F6E0\uFE0F
Improvements") will be included in the release notes.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/release.yml:
- Around line 9-24: The categories list is missing a catch-all so unlabelled PRs
are omitted; add a final category entry to the categories array (e.g., title
"Other Changes") that uses the special catch-all label '*' so any PR that didn't
match the existing label sets (the current category titles: "\U0001F6A8 Breaking
Changes", "\U0001F41B Bug Fixes", "\U0001F4D6 Documentation", "\U0001F680 New
Features", "\U0001F6E0\uFE0F Improvements") will be included in the release
notes.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fcfd4f0 and 384900a.

📒 Files selected for processing (1)
  • .github/release.yml

@AyodeAwe AyodeAwe merged commit 3358014 into NVIDIA:main Feb 23, 2026
25 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants