chore: org name change #4596

wingkwong · 2025-01-19T03:20:38Z

Closes #

📝 Description

some leftover in README

⛳️ Current behavior (updates)

🚀 New behavior

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

📝 Additional Information

Summary by CodeRabbit

Release Notes

Documentation
- Updated organization references from frontio-ai to heroui-inc across multiple packages
- Corrected contributing guidelines and license URLs in README files
- Updated changelog entries to reflect new organization name
Chores
- Systematically replaced GitHub repository links in multiple component packages
- Maintained existing dependency and version information during transition

These changes ensure consistent documentation and repository references across the HeroUI component library without altering any functional code.

changeset-bot · 2025-01-19T03:20:42Z

⚠️ No Changeset found

Latest commit: c0686b9

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 · 2025-01-19T03:20:42Z

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 3:20am
heroui-sb	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 19, 2025 3:20am

coderabbitai · 2025-01-19T03:20:48Z

Walkthrough

This pull request involves a comprehensive update of repository references from the frontio-ai organization to the heroui-inc organization across multiple component packages. The changes are primarily focused on updating URLs in documentation files such as CHANGELOG.md and README.md, specifically modifying links to contributing guidelines, licenses, and commit references. These updates ensure that all documentation points to the correct repository and organization while maintaining the existing content and structure of the files.

Changes

File Path	Change Summary
`CONTRIBUTING.md`	Updated organization URLs from `frontio-ai` to `heroui-inc`
`packages/components/*/CHANGELOG.md`	Updated organization references in commit links and dependency updates
`packages/components/*/README.md`	Updated contributing guidelines and license links to new organization

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Repo as GitHub Repository
    participant Docs as Documentation Files

    Dev->>Repo: Initiate organization transition
    Repo->>Docs: Update URLs
    Docs-->>Repo: Replace "frontio-ai" with "heroui-inc"
    Repo-->>Dev: Confirm documentation update complete

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

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

coderabbitai

Actionable comments posted: 1

🔭 Outside diff range comments (1)

packages/components/autocomplete/CHANGELOG.md (1)

Line range hint 735-764: Improve documentation for major changes.

This section contains several significant changes including:

Form validation behavior changes

Framer Motion integration updates

Calendar component addition

React Hook Form fixes

These changes deserve more detailed documentation:

Add examples for new features

Include migration guides

Document any breaking changes

Provide usage guidelines for new components

🧹 Nitpick comments (17)

packages/components/image/CHANGELOG.md (1)
467-467: Fix grammatical error in package description.

The sentence has incorrect verb form after "to".
-New package created to exports system RSC-compatible functions
+New package created to export system RSC-compatible functions
🧰 Tools

🪛 LanguageTool

[grammar] ~467-~467: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)
packages/components/calendar/CHANGELOG.md (2)

328-334: Consider adding migration notes for the framer-motion changes.

The changelog mentions several framer-motion related changes:

Replaced lodash with native approaches

Framer motion optimization

Updated framer-motion versions

Consider adding migration notes or upgrade instructions for users.

441-443: Document the global animation disable feature.

The changelog mentions adding support for disabling animations globally but doesn't provide details on how to use this feature. Consider adding usage examples or documentation references.
packages/components/link/CHANGELOG.md (1)
462-462: Fix typo in changelog entry.

There's a typo in the word "Interal" (should be "Internal").
-! - Interal hook created to control the link events
+! - Internal hook created to control the link events
🧰 Tools

🪛 LanguageTool

[uncategorized] ~462-~462: Possible missing comma found.
Context: ...ps://github.com/jrgarciadev)! - Interal hook created to control the link events - U...

(AI_HYDRA_LEO_MISSING_COMMA)
packages/components/kbd/CHANGELOG.md (1)
507-507: Fix grammar in the changelog entry.

The verb after "to" should be in the base form.
-New package created to exports system RSC-compatible functions
+New package created to export system RSC-compatible functions
🧰 Tools

🪛 LanguageTool

[grammar] ~507-~507: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)
packages/components/code/CHANGELOG.md (2)
283-288: Consider improving the changelog entry readability.

The changelog entry contains some style issues:

Redundant phrase "hook added" is repeated

Consider rephrasing "all across" to "across all" for better readability
- - objectToDeps function applied all across components
- - `useMeasure` hook added
- - `useIntersectionObserver` hook added
+ - objectToDeps function applied across all components
+ - Added `useMeasure` hook
+ - Added `useIntersectionObserver` hook
🧰 Tools

🪛 LanguageTool

[style] ~283-~283: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~284-~284: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~288-~288: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

485-487: Fix grammar in the changelog entry.

The sentence has a grammatical error in the infinitive form.
- New package created to exports system RSC-compatible functions
+ New package created to export system RSC-compatible functions
🧰 Tools

🪛 LanguageTool

[grammar] ~485-~485: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)
packages/components/input-otp/CHANGELOG.md (2)

26-30: Consider adding more context to the bug fix descriptions.

The changelog entries could benefit from more detailed explanations:

"Fix virtual keyboard to display the keys based on allowedKeys([BUG] - InputOtp keyboard on mobile #4408)" - What was the previous behavior?

"fixed isRequired not showing error" - What scenarios were affected?

"Change ensures that the input value does not accept any disallowed characters" - What types of characters were causing issues?

Line range hint 97-123: Improve the formatting of the release notes for better readability.

The release notes for version 2.1.0 contain a long list of changes. Consider structuring them into categories like:

Features

Bug Fixes

Performance Improvements

Breaking Changes
packages/components/badge/CHANGELOG.md (1)
444-444: Fix grammar in changelog entry

The verb after "to" should be in its base form.
-New package created to exports system RSC-compatible functions
+New package created to export system RSC-compatible functions
🧰 Tools

🪛 LanguageTool

[grammar] ~444-~444: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)
packages/components/chip/CHANGELOG.md (2)

Line range hint 62-88: Improve changelog formatting consistency.

Consider these formatting improvements:

Remove double dots after "bug fixes"

Avoid word repetition in hook additions

Consider rephrasing "all across" to "across all"

482-484: Fix grammatical error in changelog entry.

Change "to exports" to "to export" in the changelog entry.

🧰 Tools

🪛 LanguageTool

[grammar] ~482-~482: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)
packages/components/modal/CHANGELOG.md (1)
691-691: Fix typos and grammar in changelog entries.

There are some minor issues in the changelog entries:

Remove double dots after "bug fixes"

Consider rephrasing "to exports" to "to export" in the package creation note

Apply these corrections:
-other bug fixes..
+other bug fixes.
-New package created to exports system
+New package created to export system
🧰 Tools

🪛 LanguageTool

[typographical] ~691-~691: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)
packages/components/breadcrumbs/CHANGELOG.md (2)
Line range hint 99-184: Consider standardizing the beta version formatting.

The dependency updates in beta versions have slightly inconsistent formatting. For better readability, consider standardizing the spacing after the commit hashes.
- Updated dependencies [[`004c4a4b3`](https://github.com/heroui-inc/heroui/commit/004c4a4b3e44477f148937b12bb542e4b27fd322)]:
+ Updated dependencies [[`004c4a4b3`] (https://github.com/heroui-inc/heroui/commit/004c4a4b3e44477f148937b12bb542e4b27fd322)]:
Line range hint 3-11: Consider adding more context to the latest change.

The latest version entry (2.2.7) only mentions "Org name changed". Consider adding more context about why this change was made and its impact.
### Patch Changes

- [#4594](https://github.com/heroui-inc/heroui/pull/4594) [`7ebe0e6`](https://github.com/heroui-inc/heroui/commit/7ebe0e664feb777fe0cad311312d0e02b899319e) Thanks [@jrgarciadev](https://github.com/jrgarciadev)! - Org name changed
+ [#4594](https://github.com/heroui-inc/heroui/pull/4594) [`7ebe0e6`](https://github.com/heroui-inc/heroui/commit/7ebe0e664feb777fe0cad311312d0e02b899319e) Thanks [@jrgarciadev](https://github.com/jrgarciadev)! - Updated organization name from frontio-ai to heroui-inc across all repository references
packages/components/autocomplete/CHANGELOG.md (2)
28-28: Consider using consistent version reference format.

The version reference format in the dependency updates section differs from other entries. Consider using the same format consistently throughout the changelog.
- Updated dependencies [[`45b1d82`](https://github.com/heroui-inc/heroui/commit/45b1d82c391dac7f39609d492010164b6c2d6d38)]:
+ Updated dependencies [[`45b1d82c`](https://github.com/heroui-inc/heroui/commit/45b1d82c391dac7f39609d492010164b6c2d6d38)]:
184-184: Document architectural changes more thoroughly.

The React Aria version update across all components is a significant change that could affect the entire system. Consider:

Adding migration notes

Documenting any breaking changes

Providing examples of any new features or APIs

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 103519c and c0686b9.

📒 Files selected for processing (53)

CONTRIBUTING.md (3 hunks)
packages/components/accordion/CHANGELOG.md (46 hunks)
packages/components/accordion/README.md (1 hunks)
packages/components/alert/CHANGELOG.md (15 hunks)
packages/components/alert/README.md (1 hunks)
packages/components/autocomplete/CHANGELOG.md (48 hunks)
packages/components/autocomplete/README.md (1 hunks)
packages/components/avatar/CHANGELOG.md (24 hunks)
packages/components/avatar/README.md (1 hunks)
packages/components/badge/CHANGELOG.md (11 hunks)
packages/components/badge/README.md (1 hunks)
packages/components/breadcrumbs/CHANGELOG.md (16 hunks)
packages/components/breadcrumbs/README.md (1 hunks)
packages/components/button/CHANGELOG.md (44 hunks)
packages/components/button/README.md (1 hunks)
packages/components/calendar/CHANGELOG.md (27 hunks)
packages/components/calendar/README.md (1 hunks)
packages/components/card/CHANGELOG.md (33 hunks)
packages/components/card/README.md (1 hunks)
packages/components/checkbox/CHANGELOG.md (26 hunks)
packages/components/checkbox/README.md (1 hunks)
packages/components/chip/CHANGELOG.md (23 hunks)
packages/components/chip/README.md (1 hunks)
packages/components/code/CHANGELOG.md (24 hunks)
packages/components/code/README.md (1 hunks)
packages/components/date-input/CHANGELOG.md (8 hunks)
packages/components/date-input/README.md (1 hunks)
packages/components/date-picker/CHANGELOG.md (37 hunks)
packages/components/date-picker/README.md (1 hunks)
packages/components/divider/CHANGELOG.md (20 hunks)
packages/components/divider/README.md (1 hunks)
packages/components/drawer/CHANGELOG.md (16 hunks)
packages/components/drawer/README.md (1 hunks)
packages/components/dropdown/CHANGELOG.md (54 hunks)
packages/components/dropdown/README.md (1 hunks)
packages/components/form/CHANGELOG.md (8 hunks)
packages/components/form/README.md (1 hunks)
packages/components/image/CHANGELOG.md (23 hunks)
packages/components/image/README.md (1 hunks)
packages/components/input-otp/CHANGELOG.md (7 hunks)
packages/components/input-otp/README.md (1 hunks)
packages/components/input/CHANGELOG.md (27 hunks)
packages/components/input/README.md (1 hunks)
packages/components/kbd/CHANGELOG.md (26 hunks)
packages/components/kbd/README.md (1 hunks)
packages/components/link/CHANGELOG.md (27 hunks)
packages/components/link/README.md (1 hunks)
packages/components/listbox/CHANGELOG.md (36 hunks)
packages/components/listbox/README.md (1 hunks)
packages/components/menu/CHANGELOG.md (40 hunks)
packages/components/menu/README.md (1 hunks)
packages/components/modal/CHANGELOG.md (44 hunks)
packages/components/modal/README.md (1 hunks)

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

packages/components/date-input/README.md
packages/components/alert/README.md
packages/components/divider/README.md
packages/components/checkbox/README.md
packages/components/breadcrumbs/README.md
packages/components/listbox/README.md
packages/components/code/README.md
packages/components/input/README.md
packages/components/avatar/README.md
packages/components/input-otp/README.md
packages/components/modal/README.md
packages/components/kbd/README.md
packages/components/image/README.md
packages/components/badge/README.md
packages/components/accordion/README.md
packages/components/drawer/README.md
packages/components/button/README.md
packages/components/link/README.md
packages/components/autocomplete/README.md
packages/components/dropdown/README.md
packages/components/form/README.md
packages/components/chip/README.md
packages/components/calendar/README.md
packages/components/date-picker/README.md
packages/components/card/README.md
packages/components/drawer/CHANGELOG.md
packages/components/menu/README.md
CONTRIBUTING.md

🧰 Additional context used

🪛 LanguageTool

packages/components/input/CHANGELOG.md

[grammar] ~416-~416: The verb ‘avoids’ is used with the gerund form.
Context: ...tion changed for Select and Input, this avoids to break the layout when having long description...

(ADMIT_ENJOY_VB)

[typographical] ~604-~604: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~636-~636: It seems that the possessive pronoun “its” fits better in this context. Please verify.
Context: ...! - onValueChange returned value fixed, it nows return a plain string ## 2.0.4 #...

(IT_ITS)

[grammar] ~636-~636: Did you mean “knows” (= verb)?
Context: ... onValueChange returned value fixed, it nows return a plain string ## 2.0.4 ### Pa...

(PRP_NOWS)

[grammar] ~656-~656: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~679-~679: Using many exclamation marks might seem excessive (in this case: 67 exclamation marks for a text that’s 31910 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/accordion/CHANGELOG.md

[style] ~467-~467: Consider using a different verb for a more formal wording.
Context: ...dev](https://github.com/jrgarciadev)! - Fixed the issue where only two keyframes were...

(FIX_RESOLVE)

[typographical] ~715-~715: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~737-~737: The verb ‘avoid’ is plural. Did you mean: “avoids”? Did you use a verb instead of a noun?
Context: ... to filter non-default event/props this avoid passing non-valid props to HTML element...

(PLURAL_VERB_AFTER_THIS)

[grammar] ~772-~772: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~802-~802: Using many exclamation marks might seem excessive (in this case: 51 exclamation marks for a text that’s 33114 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/alert/CHANGELOG.md

[style] ~289-~289: Using many exclamation marks might seem excessive (in this case: 23 exclamation marks for a text that’s 13531 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - introduced Alert component (#2250) -...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/autocomplete/CHANGELOG.md

[style] ~737-~737: Consider using a different verb for a more formal wording.
Context: ...dev](https://github.com/jrgarciadev)! - Fixed the issue where only two keyframes were...

(FIX_RESOLVE)

[style] ~903-~903: Using many exclamation marks might seem excessive (in this case: 60 exclamation marks for a text that’s 43447 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - New version v2.2.0 - Updated depende...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/avatar/CHANGELOG.md

[typographical] ~454-~454: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~493-~493: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~516-~516: Using many exclamation marks might seem excessive (in this case: 36 exclamation marks for a text that’s 21082 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/badge/CHANGELOG.md

[grammar] ~444-~444: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~466-~466: Using many exclamation marks might seem excessive (in this case: 28 exclamation marks for a text that’s 18446 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/breadcrumbs/CHANGELOG.md

[style] ~284-~284: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~285-~285: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~289-~289: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[style] ~321-~321: Using many exclamation marks might seem excessive (in this case: 25 exclamation marks for a text that’s 14192 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - New version v2.2.0 - Updated depende...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/button/CHANGELOG.md

[style] ~396-~396: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~397-~397: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~401-~401: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[2e49e0831](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[typographical] ~613-~613: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~666-~666: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~693-~693: Using many exclamation marks might seem excessive (in this case: 40 exclamation marks for a text that’s 26891 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/calendar/CHANGELOG.md

[style] ~484-~484: Using many exclamation marks might seem excessive (in this case: 42 exclamation marks for a text that’s 23089 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - - Calendar component added - object...

(EN_EXCESSIVE_EXCLAMATION)

[style] ~485-~485: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~486-~486: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~490-~490: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

packages/components/card/CHANGELOG.md

[style] ~358-~358: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~359-~359: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~363-~363: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[2e49e0831](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[typographical] ~536-~536: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~586-~586: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~611-~611: Using many exclamation marks might seem excessive (in this case: 41 exclamation marks for a text that’s 25400 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/checkbox/CHANGELOG.md

[typographical] ~503-~503: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~542-~542: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~564-~564: Using many exclamation marks might seem excessive (in this case: 47 exclamation marks for a text that’s 24745 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/chip/CHANGELOG.md

[style] ~280-~280: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~281-~281: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~285-~285: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[typographical] ~443-~443: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~482-~482: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~505-~505: Using many exclamation marks might seem excessive (in this case: 33 exclamation marks for a text that’s 20086 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/code/CHANGELOG.md

[style] ~283-~283: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~284-~284: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~288-~288: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[grammar] ~485-~485: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

packages/components/date-input/CHANGELOG.md

[style] ~303-~303: Using many exclamation marks might seem excessive (in this case: 30 exclamation marks for a text that’s 15463 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - v2.3.0 - Updated dependencies [[`dc0...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/date-picker/CHANGELOG.md

[style] ~619-~619: Using many exclamation marks might seem excessive (in this case: 44 exclamation marks for a text that’s 31244 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - v2.3.0 - Updated dependencies [[`dc0...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/divider/CHANGELOG.md

[style] ~258-~258: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~259-~259: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~263-~263: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[grammar] ~472-~472: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~494-~494: Using many exclamation marks might seem excessive (in this case: 30 exclamation marks for a text that’s 20811 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/dropdown/CHANGELOG.md

[style] ~489-~489: Consider using a different verb for a more formal wording.
Context: ...dev](https://github.com/jrgarciadev)! - Fixed the issue where only two keyframes were...

(FIX_RESOLVE)

[typographical] ~747-~747: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~803-~803: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~840-~840: Using many exclamation marks might seem excessive (in this case: 60 exclamation marks for a text that’s 37254 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/form/CHANGELOG.md

[style] ~143-~143: Using many exclamation marks might seem excessive (in this case: 11 exclamation marks for a text that’s 6470 characters long)
Context: ...ryo-manba](https://github.com/ryo-manba)! - add form component

(EN_EXCESSIVE_EXCLAMATION)

packages/components/image/CHANGELOG.md

[style] ~276-~276: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~277-~277: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~281-~281: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[typographical] ~428-~428: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~467-~467: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~490-~490: Using many exclamation marks might seem excessive (in this case: 30 exclamation marks for a text that’s 19531 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/input-otp/CHANGELOG.md

[style] ~134-~134: Using many exclamation marks might seem excessive (in this case: 13 exclamation marks for a text that’s 6430 characters long)
Context: ...@macci001! - Adding new input-otp component. - Up...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/kbd/CHANGELOG.md

[grammar] ~507-~507: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~529-~529: Using many exclamation marks might seem excessive (in this case: 32 exclamation marks for a text that’s 21266 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/link/CHANGELOG.md

[style] ~321-~321: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~322-~322: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~326-~326: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[uncategorized] ~462-~462: Possible missing comma found.
Context: ...ps://github.com/jrgarciadev)! - Interal hook created to control the link events - U...

(AI_HYDRA_LEO_MISSING_COMMA)

[typographical] ~496-~496: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~535-~535: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~558-~558: Using many exclamation marks might seem excessive (in this case: 37 exclamation marks for a text that’s 22963 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/listbox/CHANGELOG.md

[style] ~442-~442: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~443-~443: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~447-~447: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[style] ~624-~624: Using many exclamation marks might seem excessive (in this case: 49 exclamation marks for a text that’s 27174 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - New components: - Select - Listb...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/menu/CHANGELOG.md

[style] ~467-~467: ‘all across’ might be wordy. Consider a shorter alternative.
Context: ...added - objectToDeps function applied all across components - useMeasure hook added ...

(EN_WORDINESS_PREMIUM_ALL_ACROSS)

[grammar] ~468-~468: This phrase is duplicated. You should probably use “hook added” only once.
Context: ... all across components - useMeasure hook added - useIntersectionObserver hook added - framer-transitions renamed to `fr...

(PHRASE_REPETITION)

[duplication] ~472-~472: Possible typo: you repeated a word.
Context: ...dded to framer-utils - test-utils updated - Updated dependencies [[dc0bcf13a](https://git...

(ENGLISH_WORD_REPEAT_RULE)

[style] ~645-~645: Using many exclamation marks might seem excessive (in this case: 47 exclamation marks for a text that’s 27957 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - New components: - Select - Listb...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/modal/CHANGELOG.md

[style] ~465-~465: Consider using a different verb for a more formal wording.
Context: ...dev](https://github.com/jrgarciadev)! - Fixed the issue where only two keyframes were...

(FIX_RESOLVE)

[typographical] ~691-~691: Two consecutive dots
Context: ...age storybooks fixed - other bug fixes.. - Updated dependencies [[a30cec48](h...

(DOUBLE_PUNCTUATION)

[grammar] ~741-~741: The verb after “to” should be in the base form as part of the to-infinitive. A verb can take many forms, but the base form is always used in the to-infinitive.
Context: .../jrgarciadev)! - New package created to exports system RSC-compatible functions Compo...

(TO_NON_BASE)

[style] ~769-~769: Using many exclamation marks might seem excessive (in this case: 55 exclamation marks for a text that’s 32257 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - Introducing v2 - Readmes updated - U...

(EN_EXCESSIVE_EXCLAMATION)

⏰ Context from checks skipped due to timeout of 90000ms (1)

GitHub Check: TypeScript

🔇 Additional comments (46)

packages/components/image/CHANGELOG.md (1)

Line range hint 1-492: Organization name change looks consistent.

The update from frontio-ai to heroui-inc has been applied consistently across all version entries in the changelog.

packages/components/menu/CHANGELOG.md (1)

Line range hint 1-652: LGTM! Organization name change is consistently applied.

The changes correctly update all repository references from frontio-ai to heroui-inc throughout the changelog, maintaining the integrity of commit hashes and PR links.

🧰 Tools

🪛 LanguageTool

[style] ~645-~645: Using many exclamation marks might seem excessive (in this case: 47 exclamation marks for a text that’s 27957 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - New components: - Select - Listb...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/calendar/CHANGELOG.md (1)

Line range hint 1-491: LGTM! The changelog entries are well-structured and consistent.

The changelog follows a clear format with:

Proper version numbering

Detailed commit references

Clear descriptions of changes

Consistent dependency updates tracking

packages/components/link/CHANGELOG.md (1)

Line range hint 1-560: LGTM! Organization name consistently updated.

The changes correctly update all repository URLs and package references from frontio-ai to heroui-inc across the changelog entries.

packages/components/kbd/CHANGELOG.md (1)

Line range hint 1-531: Organization name updates look good!

All GitHub repository URLs have been correctly updated from 'frontio-ai' to 'heroui-inc' throughout the changelog, maintaining consistency with the repository migration.

packages/components/code/CHANGELOG.md (1)

Line range hint 1-509: LGTM! Organization name changes are consistently applied.

The changes correctly update all repository URLs from 'frontio-ai' to 'heroui-inc' across the changelog entries.

packages/components/date-input/CHANGELOG.md (3)

Line range hint 1-17: LGTM! Organization name updated correctly.

The latest version entry (2.3.9) correctly reflects the organization name change from frontio-ai to heroui-inc in all GitHub URLs and dependency references.

Line range hint 18-283: LGTM! Consistent organization name updates throughout the version history.

All GitHub URLs, commit references, and dependency updates consistently use the new organization name heroui-inc.

Line range hint 289-305: LGTM! Complete and properly formatted changelog entries.

The final section maintains proper changelog formatting and consistently uses the updated organization name.

🧰 Tools

🪛 LanguageTool

[style] ~303-~303: Using many exclamation marks might seem excessive (in this case: 30 exclamation marks for a text that’s 15463 characters long)
Context: ...rciadev](https://github.com/jrgarciadev)! - v2.3.0 - Updated dependencies [[`dc0...

(EN_EXCESSIVE_EXCLAMATION)

packages/components/input-otp/CHANGELOG.md (1)

Line range hint 18-136: Organization name has been consistently updated throughout the changelog.

All GitHub repository URLs have been correctly updated from 'frontio-ai' to 'heroui-inc' across all changelog entries, maintaining proper documentation of the version history.

packages/components/card/CHANGELOG.md (1)

Line range hint 1-613: LGTM! Organization name updated consistently.

The changes correctly update all repository URLs from frontio-ai to heroui-inc across the changelog entries while maintaining the existing content and structure.

packages/components/badge/CHANGELOG.md (2)

Line range hint 1-468: Organization name changes look good!

The migration from frontio-ai to heroui-inc has been implemented consistently across all GitHub URLs, including PR links, commit references, and dependency paths.

Line range hint 1-468: Well-structured changelog entries!

The version history is thoroughly documented with:

Clear version numbers

Change types (Major/Minor/Patch)

PR references

Commit links

Dependency updates

packages/components/form/CHANGELOG.md (3)

Line range hint 1-143: Organization rename implemented consistently.

The migration from 'frontio-ai' to 'heroui-inc' has been properly implemented across all GitHub URLs, including commit links, PR references, and dependency paths.

Line range hint 3-143: Changelog structure follows best practices.

The version entries are well-organized with:

Proper semantic versioning

Clear categorization of changes (Patch/Minor)

Consistent dependency references

143-143: LGTM!

The formatting follows the standard GitHub changelog conventions.

🧰 Tools

🪛 LanguageTool

[style] ~143-~143: Using many exclamation marks might seem excessive (in this case: 11 exclamation marks for a text that’s 6470 characters long)
Context: ...ryo-manba](https://github.com/ryo-manba)! - add form component

(EN_EXCESSIVE_EXCLAMATION)

packages/components/chip/CHANGELOG.md (1)

Line range hint 1-13: LGTM! Organization name change properly documented.

The changelog correctly documents the organization name change from frontio-ai to heroui-inc along with the corresponding dependency updates.

packages/components/checkbox/CHANGELOG.md (8)

20-21: LGTM! Organization name updated correctly in dependency updates.

The organization name has been consistently updated in the dependency references while maintaining the correct version numbers and commit hashes.

28-30: LGTM! Organization name updated correctly in PR reference and commit link.

The PR reference (#4334) and commit link maintain their integrity while correctly updating the organization name.

39-41: LGTM! Organization name updated correctly in PR reference.

The PR reference (#4314) has been updated with the correct organization name while preserving the original commit information.

48-49: LGTM! Organization name updated correctly in PR reference.

The PR reference (#4311) has been updated with the correct organization name while maintaining the original commit details.

57-59: LGTM! Organization name updated correctly in PR reference and dependencies.

The PR reference (#4258) and dependency updates have been consistently updated with the new organization name.

66-68: LGTM! Organization name updated correctly in PR reference.

The PR reference (#4255) has been updated with the correct organization name while preserving the original commit information.

75-77: LGTM! Organization name updated correctly in PR reference.

The PR reference (#4247) has been updated with the correct organization name while maintaining the original commit details.

84-86: LGTM! Organization name updated correctly in commit reference.

The commit reference has been updated with the correct organization name while preserving the original commit hash and version information.

packages/components/modal/CHANGELOG.md (3)

Line range hint 1-771: Organization name changes look good!

The rebranding from frontio-ai to heroui-inc has been consistently applied across all version entries and URLs.

Line range hint 1-771: Dependency updates are well structured!

The changelog properly documents all dependency updates, including:

React-aria packages upgrades

Framer-motion version updates

Internal package version synchronization

Line range hint 1-771: Feature documentation is comprehensive!

The changelog properly categorizes and documents new features:

Clear distinction between major, minor, and patch changes

Detailed descriptions of new features and their impact

Proper attribution to contributors

packages/components/breadcrumbs/CHANGELOG.md (2)

Line range hint 1-323: Organization name changes look good!

The repository URLs have been consistently updated from frontio-ai to heroui-inc across all version entries.

Line range hint 3-323: Well-structured changelog entries!

Each version entry follows the conventional changelog format with:

Proper categorization of changes

Referenced pull requests and commit hashes

Clear descriptions of changes

packages/components/alert/CHANGELOG.md (1)

Line range hint 1-291: LGTM! Organization name consistently updated.

The changes correctly update all GitHub URLs from frontio-ai to heroui-inc while maintaining the original commit hashes and version numbers.

packages/components/avatar/CHANGELOG.md (1)

Line range hint 1-518: LGTM! Organization name consistently updated.

All references to the organization have been correctly updated to heroui-inc while preserving the version history and dependencies.

packages/components/accordion/CHANGELOG.md (1)

Line range hint 1-804: LGTM! Organization name consistently updated.

All organization references have been properly updated to heroui-inc while maintaining the integrity of version history and dependencies.

packages/components/button/CHANGELOG.md (1)

Line range hint 1-695: LGTM! Organization name consistently updated.

All organization references have been correctly updated to heroui-inc while preserving version numbers and dependency information.

packages/components/dropdown/CHANGELOG.md (1)

Line range hint 1-842: LGTM! Organization name consistently updated.

All organization references have been properly updated to heroui-inc while maintaining version history and dependency information.
packages/components/listbox/CHANGELOG.md (3)

Line range hint 1-19: LGTM! Organization name change is consistently applied.

The change from frontio-ai to heroui-inc in the latest version (2.3.10) is properly documented with corresponding dependency updates.

33-33: Important bug fix for listbox section items prop.

The fix addresses HTML element issues with listbox section items (#4277). This is a critical fix that improves component stability.

20-22: Verify React 19 compatibility across the codebase.

The bump of @tanstack/react-virtual to support React 19 peer dependencies is a significant change that may require verification across other components.

Run this script to check React version compatibility:

✅ Verification successful

React 19 compatibility is already established across the codebase

The update to @tanstack/react-virtual aligns with the existing React 19 support, as most packages already specify compatibility with React 19 through their peer dependencies (>=18 || >=19.0.0-rc.0).
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:
#!/bin/bash
# Description: Check React version compatibility across the codebase

# Check package.json files for React version ranges
fd package.json --exec jq -r '.peerDependencies.react, .dependencies.react'

# Check for any potential React version conflicts
rg -A 5 "peerDependencies.*react.*"
Length of output: 2955
packages/components/divider/CHANGELOG.md (3)

Line range hint 1-13: LGTM! Organization name change properly documented.

The changelog correctly documents the organization name change and its corresponding dependency updates.

Line range hint 14-496: LGTM! Well-maintained changelog with detailed version history.

The changelog follows good practices including:

Proper semantic versioning

Detailed descriptions of changes

Consistent dependency tracking

Line range hint 1-496: Verify all repository URLs are updated.

All URLs appear to be updated to the new organization name. Let's verify there are no remaining references to the old organization name.

✅ Verification successful

All repository URLs are updated correctly

All GitHub URLs in the codebase have been updated to use the new organization name "heroui-inc". No references to the old organization name remain.
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:
#!/bin/bash
# Description: Check for any remaining references to the old organization name

# Search for any remaining instances of the old org name
rg -i "frontio-ai"

# Verify all GitHub URLs use the new org name
rg -i "github.com/[^/]+/heroui"
Length of output: 97634
packages/components/date-picker/CHANGELOG.md (2)

Line range hint 1-621: LGTM! The changelog follows proper versioning and formatting.

The changelog is well-structured and follows semantic versioning conventions. The organization name change from frontio-ai to heroui-inc has been consistently applied across all versions and dependencies.

24-24: Verify dependency updates for potential breaking changes.

The changelog includes numerous dependency updates across versions. Let's verify these updates for any potential breaking changes or security issues.

Run the following script to check for any security advisories in the updated dependencies:

Also applies to: 37-37, 51-51, 62-62, 73-73, 84-84, 98-98, 112-112, 126-126, 169-169, 171-171, 173-173, 190-190, 201-201, 215-215, 232-232, 246-246, 267-267, 283-283, 299-299, 315-315, 326-326, 339-339, 355-355, 371-371, 378-378, 394-394, 398-398, 400-400, 402-402, 419-419, 432-432, 446-446, 462-462, 483-483, 485-485, 487-487, 502-502, 504-504, 506-506, 521-521, 532-532, 536-536, 538-538, 540-540, 542-542, 544-544, 546-546, 548-548, 561-561, 563-563, 575-575, 586-586, 593-593, 600-600, 613-613, 619-619

✅ Verification successful

Dependencies verified - no breaking changes or security issues found

The dependency updates are internal workspace changes within the monorepo. No security vulnerabilities or breaking changes were detected in the codebase. The external dependencies maintain consistent version ranges and follow proper semantic versioning.
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:
#!/bin/bash
# Description: Check for security advisories in the updated dependencies

# Get list of @heroui scoped packages from the changelog
packages=$(cat packages/components/date-picker/CHANGELOG.md | grep -o '@heroui/[a-zA-Z0-9-]*' | sort -u)

# Check for security advisories for each package
for package in $packages; do
  echo "Checking $package..."
  gh api graphql -f query='
  {
    securityVulnerabilities(first: 5, ecosystem: PIP, package: "'${package}'") {
      nodes {
        advisory {
          summary
          severity
          publishedAt
        }
        vulnerableVersionRange
        firstPatchedVersion {
          identifier
        }
      }
    }
  }'
done
Length of output: 6015

Script:
#!/bin/bash
# Get the commit details for the dependency updates
for commit in 33e0418 e7ff673 fb46df2; do
  echo "=== Commit $commit ==="
  git show --no-patch --format="%h %s" $commit
  git show --stat $commit
done
Length of output: 1631

Script:
#!/bin/bash
# Find and check package.json files in the components directory
echo "=== Checking package.json files ==="
fd package.json packages/components/ --exec cat {} \; 

echo -e "\n=== Checking CHANGELOG.md for breaking changes ==="
rg "BREAKING CHANGE" packages/components/date-picker/CHANGELOG.md -B 1 -A 2
Length of output: 67631
packages/components/input/CHANGELOG.md (3)

34-34: Verify the label placement for file input type.

The fix for label placement with file input type needs verification to ensure proper alignment and positioning.

Run the following script to check the implementation:

✅ Verification successful

Label placement implementation for file input type is properly handled

The implementation correctly handles label placement for file input type by:

Treating file inputs as always filled to maintain proper styling and label positioning

Using the same consistent label placement logic as other input types

Properly managing the input's visual state
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:
#!/bin/bash
# Description: Check label placement implementation for file input type.

# Search for file input type label placement logic
ast-grep --pattern 'type === "file"'
rg -A 5 'labelPlacement.*file'
Length of output: 161

Script:
#!/bin/bash
# Get more context around file input handling and label placement

# Check the usage of isFileTypeInput
ast-grep --pattern 'const isFileTypeInput = type === "file"
  $$$'

# Find label placement related code in the input component
rg -B 5 -A 10 'labelPlacement' packages/components/input/src/

# Look for file input specific styles
rg -A 5 'file.*input' packages/components/input/src/
Length of output: 9025

Script:
#!/bin/bash
# Get the complete context around isFileTypeInput usage and label placement

# Get more context around isFileTypeInput
rg -B 10 -A 10 'isFileTypeInput' packages/components/input/src/

# Check for any file input specific styling or class names
ast-grep --pattern 'className = $$$file$$$'
Length of output: 5477
20-20: Verify the input space handling fix.

Let's ensure the fix for input ignoring spaces is working as expected.

Run the following script to check the implementation:

567-567: Verify uncontrolled input behavior.

The change to support uncontrolled input behavior through ref mutations needs thorough testing.

Run the following script to check the implementation:

✅ Verification successful

Verified: Input component now properly supports both controlled and uncontrolled modes

The implementation correctly supports mutations via ref while maintaining controlled state functionality when needed. The component synchronizes its internal state with ref.current.value changes, allowing for proper uncontrolled behavior when desired.
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:
#!/bin/bash
# Description: Check controlled/uncontrolled input implementation.

# Search for controlled/uncontrolled handling
ast-grep --pattern 'const [controlled, setControlled]'
rg -A 5 'useControlled|useUncontrolled'
Length of output: 7161

Script:
#!/bin/bash
# Check ref implementation in input component
ast-grep --pattern 'useImperativeHandle($_, $_, $_)'
rg -A 10 'useImperativeHandle.*Input' 
Length of output: 94

Script:
#!/bin/bash
# Examine input component implementation
ast-grep --pattern 'function Input($$$)'
rg -A 10 'export.*function.*Input.*\{' 
rg -A 5 'ref.*=.*useRef'
Length of output: 8146

Script:
#!/bin/bash
# Find and examine input component implementation
fd -e ts -e tsx "input.ts" -x cat {}
rg -A 10 "export.*Input.*=.*" packages/components/input/src/
Length of output: 78065

coderabbitai · 2025-01-19T03:31:54Z

packages/components/autocomplete/CHANGELOG.md

+- [#4458](https://github.com/heroui-inc/heroui/pull/4458) [`7c2bc4a`](https://github.com/heroui-inc/heroui/commit/7c2bc4a18ef01424c7ff464cad3401dd6596e7b3) Thanks [@wingkwong](https://github.com/wingkwong)! - clear autocomplete value when pressing clear button (#4402)

- [#4452](https://github.com/frontio-ai/heroui/pull/4452) [`0401f25`](https://github.com/frontio-ai/heroui/commit/0401f2548f525fc4194186b54f563cb91c6ccd0c) Thanks [@Peterl561](https://github.com/Peterl561)! - fixed autocomplete validate prop not working after hovering when validation behavior is native
+- [#4452](https://github.com/heroui-inc/heroui/pull/4452) [`0401f25`](https://github.com/heroui-inc/heroui/commit/0401f2548f525fc4194186b54f563cb91c6ccd0c) Thanks [@Peterl561](https://github.com/Peterl561)! - fixed autocomplete validate prop not working after hovering when validation behavior is native

- [#4462](https://github.com/frontio-ai/heroui/pull/4462) [`16c57ec`](https://github.com/frontio-ai/heroui/commit/16c57ece6467d755645f109b8de810c9063e5665) Thanks [@vinroger](https://github.com/vinroger)! - add support for dataset with section, add support for scrollshadow
+- [#4462](https://github.com/heroui-inc/heroui/pull/4462) [`16c57ec`](https://github.com/heroui-inc/heroui/commit/16c57ece6467d755645f109b8de810c9063e5665) Thanks [@vinroger](https://github.com/vinroger)! - add support for dataset with section, add support for scrollshadow

- [#4496](https://github.com/frontio-ai/heroui/pull/4496) [`0c45fed`](https://github.com/frontio-ai/heroui/commit/0c45fed420747b41a4d2a7bb07e9582f6f609287) Thanks [@wingkwong](https://github.com/wingkwong)! - fix missing popover props except content (#4484)
+- [#4496](https://github.com/heroui-inc/heroui/pull/4496) [`0c45fed`](https://github.com/heroui-inc/heroui/commit/0c45fed420747b41a4d2a7bb07e9582f6f609287) Thanks [@wingkwong](https://github.com/wingkwong)! - fix missing popover props except content (#4484)


⚠️ Potential issue

Critical bug fixes need more detailed descriptions.

These bug fixes address important functionality but lack detailed explanations of:

The root cause of the clear button issue

The validation behavior changes

The dataset section support implementation

The missing popover props impact

Consider adding more context about each fix to help users understand the impact and whether they need to update their implementations.

chore: org name change

c0686b9

wingkwong requested a review from jrgarciadev as a code owner January 19, 2025 03:20

coderabbitai bot reviewed Jan 19, 2025

View reviewed changes

jrgarciadev approved these changes Jan 19, 2025

View reviewed changes

jrgarciadev merged commit cf39e22 into canary Jan 19, 2025
8 checks passed

jrgarciadev deleted the chore/org-change branch January 19, 2025 12:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: org name change #4596

chore: org name change #4596

wingkwong commented Jan 19, 2025 •

edited by coderabbitai bot

Loading

changeset-bot bot commented Jan 19, 2025

vercel bot commented Jan 19, 2025

coderabbitai bot commented Jan 19, 2025 •

edited

Loading

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

Documentation and Community

coderabbitai bot left a comment

coderabbitai bot Jan 19, 2025

chore: org name change #4596

chore: org name change #4596

Conversation

wingkwong commented Jan 19, 2025 • edited by coderabbitai bot Loading

📝 Description

⛳️ Current behavior (updates)

🚀 New behavior

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

📝 Additional Information

Summary by CodeRabbit

Release Notes

changeset-bot bot commented Jan 19, 2025

⚠️ No Changeset found

vercel bot commented Jan 19, 2025

coderabbitai bot commented Jan 19, 2025 • edited Loading

Walkthrough

Changes

Sequence Diagram

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

Documentation and Community

coderabbitai bot left a comment

Choose a reason for hiding this comment

coderabbitai bot Jan 19, 2025

Choose a reason for hiding this comment

wingkwong commented Jan 19, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Jan 19, 2025 •

edited

Loading