chore(deps): bump doom to v1.11.0

[JounQin]

Summary by CodeRabbit

• Chores
  • Upgraded package manager to Yarn 4.9.4 for improved consistency and reliability.
  • Updated dependencies to latest compatible versions (e.g., @alauda/doom, @types/react-dom) to maintain stability and compatibility.
  • Added lightweight git hook management to run pre-commit checks automatically, enhancing developer experience and code quality.

[coderabbitai]

Walkthrough

Bumped Yarn from 4.9.3 to 4.9.4 in configuration and package manager field. Updated dependencies in package.json, including @alauda/doom and @types/react-dom. Added simple-git-hooks as a devDependency. No exported/public API changes.

Changes

Cohort / File(s)	Summary of changes
Yarn version bump ./.yarnrc.yml	Updated yarnPath from .yarn/releases/yarn-4.9.3.cjs to .yarn/releases/yarn-4.9.4.cjs.
Package manager metadata ./package.json	Changed packageManager from yarn@4.9.3 to yarn@4.9.4.
Dependencies update ./package.json	Bumped @alauda/doom from ^1.10.12 to ^1.11.0; updated @types/react-dom from ^19.1.7 to ^19.1.8.
Dev tooling ./package.json	Added devDependency simple-git-hooks@^2.13.1; pre-commit hook remains configured.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• chore: bump doom to v1.10.11 #86 — Also updates package.json to bump @alauda/doom (to ^1.10.11), indicating related dependency version alignment work.

Poem

I twitch my whiskers, hop in delight,
Yarn hops a notch—4.9.4 feels right.
Doom gets a lift, hooks click in place,
Tiny tweaks tidy the project’s pace.
Thump-thump! says the repo, crisp and neat,
Carrots compiled—dependencies complete. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/deps

---

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

🪧 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>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• 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.
• 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

package.json (1)

26-26: Add a TypeScript “noEmit” check to CI for React 19.x types

Since you do have a tsconfig.json in the repo, it’s a good idea to enforce a full type-check in CI to catch any mismatches with the experimental React 19.x typings. Here’s how you might integrate it:

• In your CI configuration (e.g. GitHub Actions, CircleCI), add a step that runs:

yarn -s tsc --noEmit

• Alternatively, you can expose this as an npm script in package.json:

  "scripts": {
+   "type-check": "tsc --noEmit",
    "build": "…",
    "test": "…"
  }

Then call yarn type-check in CI as part of your pipeline.

This ensures any incompatibility between @types/react-dom@^19.1.8 and your code surfaces immediately.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d11b01e and 18557c2.

⛔ Files ignored due to path filters (2)

• .yarn/releases/yarn-4.9.4.cjs is excluded by !**/.yarn/**
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

• .yarnrc.yml (1 hunks)
• package.json (3 hunks)

🔇 Additional comments (3)

.yarnrc.yml (1)

12-12: Yarn 4.9.4 bump verified – ready to merge
All checks passed: the version in .yarnrc.yml and package.json match, the yarn-4.9.4.cjs binary is present under .yarn/releases, and the plugin-prepare-lifecycle entry remains configured.

Feel free to merge. Contributors should still ensure Corepack is enabled (e.g. corepack enable && corepack prepare yarn@4.9.4 --activate) to prevent any version drift.

package.json (2)

5-5: packageManager → yarn@4.9.4 — looks good.

Matches .yarnrc.yml. Keep the Yarn release file committed to prevent CI/local skew. The verification script in the .yarnrc.yml comment covers this.

---

16-16: @alauda/doom upgraded to ^1.11.0 — peers are clear, now smoke-test the toolchain

• Verified the dependency bump in package.json: ^1.11.0
• Confirmed latest published version is 1.11.0 with no peerDependencies → no new peer constraints introduced
• Noted new engines.node requirement: >=18.17.0 <20 || >=20.1.0 — ensure your local Node version fits this range

Please run a quick smoke build (React/Node/MDX toolchain) to catch any unforeseen breakages.

[cloudflare-workers-and-pages]

Deploying acp-docs with    Cloudflare Pages

Latest commit:	18557c2
Status:	✅  Deploy successful!
Preview URL:	https://bf99eb2e.acp-docs.pages.dev
Branch Preview URL:	https://chore-deps.acp-docs.pages.dev

View logs