Add wrapperbot and update workflow order

[juherr]

Summary by CodeRabbit

• Chores
  • Scheduled Dependabot to check updates daily at 00:00 UTC.
  • Adjusted the execution time of the combine PRs workflow to 02:00 UTC and introduced a new input parameter for branch filtering.
  • Implemented a daily workflow to automatically update the Gradle Wrapper at 00:00 UTC.

[coderabbitai]

Warning

Rate Limit Exceeded

@juherr has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 28 minutes and 10 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 2e5614f and 32408da.

Walkthrough

This update introduces precise scheduling for dependency checks and workflow executions, ensuring timely updates and efficient integration processes. By specifying exact times for npm updates and adjusting workflow schedules, it streamlines operations. Additionally, a new workflow for updating the Gradle Wrapper enhances project consistency and reliability, keeping the build system up-to-date automatically.

Changes

File Path	Change Summary
.github/dependabot.yml	Added a schedule for npm updates at 00:00 UTC.
.github/workflows/...	Adjusted execution time to 02:00 UTC for combine-prs.yml; added branch_regex input.
	Introduced "Update Gradle Wrapper" workflow in update-gradle-wrapper.yml running daily at 00:00 UTC.

Poem

In the moon's soft glow, at midnight's strike,
🌙 Bits and bytes dance, updates take flight.
With schedules set and patterns matched,
🐇 CodeRabbit's garden, perfectly patched.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between f5a46d5 and 2e5614f.

Files selected for processing (3)

• .github/dependabot.yml (1 hunks)
• .github/workflows/combine-prs.yml (2 hunks)
• .github/workflows/update-gradle-wrapper.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/dependabot.yml

Additional comments: 4

.github/workflows/update-gradle-wrapper.yml (2)

• 5-5: Ensure the scheduled time of '0 0 * * *' aligns with the intended update frequency and does not conflict with other scheduled workflows.
• 15-15: Confirm gradle-update/update-gradle-wrapper-action@v1 is the latest and most secure version of the action to use for updating the Gradle Wrapper.

.github/workflows/combine-prs.yml (2)

• 5-5: Verify the change in schedule to '0 2 * * *' does not cause unintended delays or overlaps with other workflows.
• 22-22: Ensure the regex pattern ^(dependa|wrapper)bot\/.*$ accurately captures all intended branches for the combine-prs workflow without excluding any relevant branches or including unintended ones.