Skip to content

Conversation

@kmonahan
Copy link
Collaborator

No description provided.

@kmonahan kmonahan merged commit cb6a613 into 2.x Sep 15, 2025
1 check was pending
@coderabbitai
Copy link

coderabbitai bot commented Sep 15, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

This change standardizes Node.js to version 22 across development and CI: .nvmrc, .ddev/config.yaml, Dockerfile (node:22-alpine), GitHub Actions setup-node, and package.json engines. package.json updates version to 2.2.0, upgrades Next.js to 15.5.2, Storybook packages to 9.1.4, TypeScript to ~5.9.2, and various linters/types. The prettier check script target changes from pages to app. next-env.d.ts adds a reference to .next/types/routes.d.ts. .gitignore adds storybook/ alongside storybook-static/. No other configuration files are modified.

✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 2.x-RC

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Jira 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 d3ce7d1 and fdb74cf.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (7)
  • .ddev/config.yaml (1 hunks)
  • .github/workflows/publish-demo-site.yml (1 hunks)
  • .gitignore (1 hunks)
  • .nvmrc (1 hunks)
  • Dockerfile (1 hunks)
  • next-env.d.ts (1 hunks)
  • package.json (3 hunks)

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.


Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants