Upgrade Drill App Agent to 0.9.9 and Drill Agent to 0.23.8

[iryabov]

Summary by CodeRabbit

• Chores
  • Updated internal agent dependencies to newer versions for improved compatibility and stability.
  • No functional or UI changes expected for end-users.

[coderabbitai]

Walkthrough

Updated dependency versions in build.gradle: enableTestAgent.version from 0.23.5 to 0.23.8 and enableAppAgent.version from 0.9.7 to 0.9.9.

Changes

Cohort / File(s)	Summary of changes
Build configuration build.gradle	Bumped enableTestAgent.version 0.23.5 → 0.23.8 and enableAppAgent.version 0.9.7 → 0.9.9.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nudge the dials, hop-hop—so neat,
Versions rise like carrots sweet.
0.23 to 0.23.8, I cheer,
0.9.7 hops to .9—so near!
Build burrows hum, my paws at rest,
Small bumps made swift—now pass the test. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly and concisely summarizes the main change by specifying the new versions for both the Drill App Agent and Drill Agent, matching the changes made in build.gradle without including unnecessary details.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch drill/version-0.9.9

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8a90473 and 6af6771.

📒 Files selected for processing (1)

• build.gradle (1 hunks)

🔇 Additional comments (1)

build.gradle (1)

214-219: Drill agents bumped to latest patch.

Looks good—nothing else in the drill block needs adjusting for these version bumps.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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 and usage tips.}