Skip to content

chore: bump Gradle wrapper to 9.6.1 and add PR template - #26

Merged
jamesarich merged 1 commit into
mainfrom
chore/wrapper-and-templates
Jul 23, 2026
Merged

chore: bump Gradle wrapper to 9.6.1 and add PR template#26
jamesarich merged 1 commit into
mainfrom
chore/wrapper-and-templates

Conversation

@jamesarich

Copy link
Copy Markdown
Collaborator

Summary

Standards-compliance hygiene fixes (no code changes).

  • Gradle wrapper 9.5.1 → 9.6.1 (§1.1): properties-only edit to gradle/wrapper/gradle-wrapper.properties — bumped distributionUrl to the 9.6.1 -bin distribution and updated distributionSha256Sum to the matching checksum. gradlew/gradlew.bat scripts untouched.
  • Add .github/PULL_REQUEST_TEMPLATE.md (§8.4): summary / type of change / affirmations checklist (DCO, apiDump, build), adapted for kzstd.
  • Enable Renovate vulnerabilityAlerts (§5.6) in .github/renovate.json.

Type of change

  • Infrastructure / CI / build

Affirmations

  • All commits are signed off (DCO).

- Bump Gradle wrapper 9.5.1 -> 9.6.1 (-bin), matching checksum (§1.1)
- Add .github/PULL_REQUEST_TEMPLATE.md with summary/type/checklist (§8.4)
- Enable renovate vulnerabilityAlerts in .github/renovate.json (§5.6)

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@jamesarich
jamesarich enabled auto-merge July 23, 2026 00:46
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 49 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: 7dfa8f99-aef8-4f1c-8760-4e41fbafca6b

📥 Commits

Reviewing files that changed from the base of the PR and between 14c0317 and e137f3d.

📒 Files selected for processing (3)
  • .github/PULL_REQUEST_TEMPLATE.md
  • .github/renovate.json
  • gradle/wrapper/gradle-wrapper.properties

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.

@jamesarich
jamesarich added this pull request to the merge queue Jul 23, 2026
Merged via the queue into main with commit 9cbb68d Jul 23, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant