chore(docs): update nav banner

[wingkwong]

Closes #

📝 Description

⛳️ Current behavior (updates)

🚀 New behavior

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

• New Features
  • Updated the banner displayed at the top of the application layout with an improved version.

[linear]

ENG-2856 remove chat banner from v2 docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7079bd1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
heroui	Ready	Preview	Comment	Oct 21, 2025 3:15am
heroui-sb	Ready	Preview	Comment	Oct 21, 2025 3:15am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

[coderabbitai]

Walkthrough

The pull request replaces the RandomBanner component with ProBanner in the root layout file. The import statement and JSX rendering are updated to use the new banner component, with no changes to surrounding structure or logic.

Changes

Cohort / File(s)	Change Summary
Banner Component Substitution apps/docs/app/layout.tsx	Replaced RandomBanner import and component reference with ProBanner in the root layout

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• jrgarciadev

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description consists entirely of the template structure with placeholder comments and no actual filled-in content. All required sections—Description, Current behavior, New behavior, Breaking change indicator, and Additional Information—remain empty with only their template guidance comments. This fails to provide reviewers with meaningful context about why the change was made, what specifically is being updated, or the rationale for the modification.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "chore(docs): update nav banner" directly corresponds to the changeset, which replaces the RandomBanner component with ProBanner in the docs layout file. The title appropriately describes the update to a banner component in the documentation section. While the title could be more specific about the nature of the update (e.g., which banner component is being replaced), it is clear and specific enough that a teammate reviewing the commit history would understand this involves modifying a banner component.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/eng-2856

---

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.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between acd5f1d and 7079bd1.

📒 Files selected for processing (1)

• apps/docs/app/layout.tsx (2 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

apps/docs/app/layout.tsx (1)

apps/docs/components/pro-banner.tsx (1)

• ProBanner (13-117)

🔇 Additional comments (1)

apps/docs/app/layout.tsx (1)

86-86: LGTM! Component placement is appropriate.

The ProBanner component is correctly positioned at the top of the layout before the navbar, which is the expected placement for a promotional banner.