chore: update brand name

[wingkwong]

Closes #

📝 Description

⛳️ Current behavior (updates)

🚀 New behavior

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

📝 Additional Information

Summary by CodeRabbit

• Branding

  • Updated brand name from "Next UI" to "Hero UI" across multiple files
  • Added "hero ui" keyword to package metadata

• Documentation

  • Updated copyright notices in LICENSE files to include "Inc."

• Chores

  • Modified console warning prefix from "[Next UI]" to "[Hero UI]"

These changes reflect a comprehensive rebranding effort across the project's documentation and core utilities.

[changeset-bot]

🦋 Changeset detected

Latest commit: e103831

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 58 packages

Name	Type
@heroui/shared-utils	Patch
@heroui/accordion	Patch
@heroui/alert	Patch
@heroui/autocomplete	Patch
@heroui/avatar	Patch
@heroui/badge	Patch
@heroui/breadcrumbs	Patch
@heroui/button	Patch
@heroui/calendar	Patch
@heroui/card	Patch
@heroui/checkbox	Patch
@heroui/chip	Patch
@heroui/code	Patch
@heroui/date-input	Patch
@heroui/date-picker	Patch
@heroui/divider	Patch
@heroui/drawer	Patch
@heroui/dropdown	Patch
@heroui/form	Patch
@heroui/image	Patch
@heroui/input-otp	Patch
@heroui/input	Patch
@heroui/kbd	Patch
@heroui/link	Patch
@heroui/listbox	Patch
@heroui/menu	Patch
@heroui/modal	Patch
@heroui/navbar	Patch
@heroui/pagination	Patch
@heroui/popover	Patch
@heroui/progress	Patch
@heroui/radio	Patch
@heroui/ripple	Patch
@heroui/scroll-shadow	Patch
@heroui/select	Patch
@heroui/skeleton	Patch
@heroui/slider	Patch
@heroui/snippet	Patch
@heroui/spacer	Patch
@heroui/spinner	Patch
@heroui/switch	Patch
@heroui/table	Patch
@heroui/tabs	Patch
@heroui/tooltip	Patch
@heroui/user	Patch
@heroui/theme	Patch
@heroui/use-aria-button	Patch
@heroui/use-aria-link	Patch
@heroui/use-data-scroll-overflow	Patch
@heroui/use-infinite-scroll	Patch
@heroui/use-pagination	Patch
@heroui/aria-utils	Patch
@heroui/framer-utils	Patch
@heroui/react-utils	Patch
@heroui/react	Patch
@heroui/system	Patch
@heroui/use-image	Patch
@heroui/use-real-shape	Patch

Not sure what this means? Click here to learn what changesets are.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
heroui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 19, 2025 2:30pm
heroui-sb	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 19, 2025 2:30pm

[coderabbitai]

Walkthrough

The pull request introduces a comprehensive rebranding effort from "Next UI" to "Hero UI" across multiple files. The changes include updating copyright notices in LICENSE files, modifying package keywords, updating comments in test files, and changing console warning prefixes. These modifications appear to be part of a systematic renaming process that touches various components of the project infrastructure.

Changes

File	Change Summary
.changeset/dry-kings-add.md	Patch update for @heroui/shared-utils package
LICENSE	Copyright notice updated from "Next UI" to "Next UI Inc."
apps/docs/LICENSE	Copyright notice updated from "Next UI" to "Next UI Inc."
packages/components/dropdown/__tests__/dropdown.test.tsx	Comments updated from "Next UI Element" to "Hero UI Element"
packages/core/react/package.json	Added keyword "hero ui" to package keywords
packages/utilities/shared-utils/src/console.ts	Warning log prefix changed from [Next UI] to [Hero UI]

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Proj as Project Files
    
    Dev->>Proj: Update branding
    Proj-->>Dev: Modify copyright notices
    Proj-->>Dev: Update package keywords
    Proj-->>Dev: Change comments and log prefixes

Loading

The sequence diagram illustrates the systematic process of updating branding across project files, showing how a developer would systematically modify various components to reflect the new brand name.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf39e22 and e103831.

📒 Files selected for processing (6)

• .changeset/dry-kings-add.md (1 hunks)
• LICENSE (1 hunks)
• apps/docs/LICENSE (1 hunks)
• packages/components/dropdown/__tests__/dropdown.test.tsx (2 hunks)
• packages/core/react/package.json (1 hunks)
• packages/utilities/shared-utils/src/console.ts (1 hunks)

✅ Files skipped from review due to trivial changes (6)

• .changeset/dry-kings-add.md
• packages/utilities/shared-utils/src/console.ts
• packages/core/react/package.json
• LICENSE
• apps/docs/LICENSE
• packages/components/dropdown/tests/dropdown.test.tsx

---

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>, please review it.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code 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 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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.

Documentation and Community

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