-
Notifications
You must be signed in to change notification settings - Fork 105
Update dependabot and release template configuration #806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependabot and release template configuration #806
Conversation
WalkthroughConfiguration-only updates: Dependabot config adjusted to drop the skip-changelog label across specified update blocks; release-draft template updated to add a dependencies label to a category and remove Dependabot-related replacer rules. No schedule, strategy, or template content changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
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. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.github/dependabot.yml
(0 hunks).github/release-draft-template.yml
(1 hunks)
💤 Files with no reviewable changes (1)
- .github/dependabot.yml
🔇 Additional comments (2)
.github/release-draft-template.yml (2)
38-42
: Replacer scope looks good.Keeping only meili-bors/meili-bot replacers and dropping Dependabot variants aligns with the PR goal and Release Drafter’s replacer format. (github.com)
4-5
: Confirm intent to retainskip-changelog
inexclude-labels
.If Dependabot no longer sets this label, keeping it is harmless but redundant; remove it if you intend to retire the label entirely. (coder.social)
label: | ||
- "dependencies" | ||
- "maintenance" | ||
- "documentation" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use labels:
(plural) when providing a list.
Release Drafter expects label: "<single label>"
or labels: [..]
. Here, label:
is mapped to a YAML sequence, which is undocumented and may be ignored. Switch to labels:
to ensure all three labels are recognized. (github.com)
Apply this diff:
- title: "⚙️ Maintenance/misc"
- label:
+ labels:
- "dependencies"
- "maintenance"
- "documentation"
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
label: | |
- "dependencies" | |
- "maintenance" | |
- "documentation" | |
labels: | |
- "dependencies" | |
- "maintenance" | |
- "documentation" |
🤖 Prompt for AI Agents
In .github/release-draft-template.yml around lines 26 to 29, the template uses
"label:" mapped to a YAML sequence which Release Drafter expects as either a
single "label:" string or "labels:" array; update the key from "label:" to
"labels:" so the three entries are treated as a list (labels:
["dependencies","maintenance","documentation"]) and ensure YAML syntax remains a
sequence of strings.
This PR is auto-generated.
This PR makes two changes:
These changes improve dependency management and release categorization.
Summary by CodeRabbit