[kiview]

Exclude gradle-wrapper from Dependabot updates so Gradle upgrades do not enter the general dependency batch, as happened in #12067. Wrapper upgrades remain handled by the existing dedicated Update Gradle Wrapper workflow.

Add the exclusion to the root, examples, and smoke-test entries. The examples and smoke-test builds include the root build, so their scans also discover its wrapper. Existing dependency exclusions and the dedicated workflow remain unchanged.

Summary by CodeRabbit

• Chores
  • Adjusted automated dependency update settings so Gradle wrapper upgrades are handled through the dedicated workflow.

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: bd99160b-c57d-4879-bad6-4714acbac34f

📥 Commits

Reviewing files that changed from the base of the PR and between 213c89b and acf6a5a.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: f3e74f97-018a-45e6-adb0-ce556088c965

📥 Commits

Reviewing files that changed from the base of the PR and between 8e54951 and 213c89b.

📒 Files selected for processing (1)

• .github/dependabot.yml

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

📝 Walkthrough

Dependabot now ignores gradle-wrapper updates in the root, /examples, and /smoke-test Gradle update blocks. A comment states that wrapper upgrades use the separate Update Gradle Wrapper workflow.

Changes: Gradle Wrapper Update Coordination

Layer / File(s)	Summary
Dependabot wrapper exclusions .github/dependabot.yml	The root, /examples, and /smoke-test Gradle update blocks now ignore gradle-wrapper updates.

Priority: ⬇️ Low

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

Change: Other

Suggested reviewers: eddumelendez

Merge Risk: ⚪ Minimal · up to 213c8

This configuration change keeps wrapper upgrades on the dedicated workflow without introducing an established runtime or delivery risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly and concisely describes the main change: excluding the Gradle wrapper from Dependabot updates.
Description check	✅ Passed	The description explains the change, its context, affected Dependabot entries, and the existing workflow that remains responsible for wrapper upgrades.

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