Bump lucide-react-native from 0.462.0 to 0.577.0#282
Bump lucide-react-native from 0.462.0 to 0.577.0#282dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [lucide-react-native](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react-native) from 0.462.0 to 0.577.0. - [Release notes](https://github.com/lucide-icons/lucide/releases) - [Commits](https://github.com/lucide-icons/lucide/commits/0.577.0/packages/lucide-react-native) --- updated-dependencies: - dependency-name: lucide-react-native dependency-version: 0.577.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
There was a problem hiding this comment.
AI Code Review by LlamaPReview
🎯 TL;DR & Recommendation
Recommendation: Request Changes
This PR updates lucide-react-native with breaking changes that could cause runtime icon failures and introduces version mismatches with lucide-react, risking cross-platform UI bugs.
🌟 Strengths
- Routine dependency update to benefit from latest features and fixes.
| Priority | File | Category | Impact Summary | Anchors |
|---|---|---|---|---|
| P1 | packages/ui/package.json | Architecture | Breaking icon renames could silently fail existing icon renders at runtime. | path:packages/ui/icons/index.native.tsx |
| P2 | packages/ui/package.json | Architecture | Namespace export removal may break icon import patterns if not verified. | |
| P2 | packages/ui/package.json | Maintainability | Version mismatch with lucide-react risks cross-platform UI inconsistencies. | |
| P2 | pnpm-lock.yaml | Maintainability | Large lockfile delta increases merge conflict risk and indirect dependency bugs. | |
| P2 | packages/ui/package.json | Testing | Missing test changes may lead to snapshot failures and untested regressions. |
🔍 Notable Themes
- Dependency Management: This update highlights risks associated with major version jumps, including breaking changes, cross-platform consistency, and merge conflicts from lockfile changes.
📈 Risk Diagram
This diagram illustrates the risk of icon rendering failures due to renamed icons after the version update.
sequenceDiagram
participant UI as UI Component
participant IL as lucide-react-native
participant EU as End User
UI->>IL: import icon("flip-horizontal")
IL->>IL: lookup icon (version 0.577.0)
note over IL: R1(P1): Icon "flip-horizontal" renamed to<br/>"square-centerline-dashed-horizontal"
IL-->>UI: icon not found or default
UI->>EU: render broken or missing icon
⚠️ **Unanchored Suggestions (Manual Review Recommended)**
The following suggestions could not be precisely anchored to a specific line in the diff. This can happen if the code is outside the changed lines, has been significantly refactored, or if the suggestion is a general observation. Please review them carefully in the context of the full file.
📁 File: pnpm-lock.yaml
The PR includes substantial changes to pnpm-lock.yaml (81 additions, 28 deletions). While expected for a dependency update, this large delta increases merge conflict risk for other concurrent PRs. It also transitively updates many sub-dependencies of lucide-react-native. There is a risk that an indirect dependency update introduces its own breaking change or bug. A thorough CI run (including integration and visual tests for icons) is essential before merging.
Related Code:
💡 Have feedback? We'd love to hear it in our GitHub Discussions.
✨ This review was generated by LlamaPReview Advanced, which is free for all open-source projects. Learn more.
| "lucide-react": "^0.563.0", | ||
| "lucide-react-native": "^0.462.0", | ||
| "lucide-react-native": "^0.577.0", | ||
| "markdown-to-jsx": "^7.7.13", |
There was a problem hiding this comment.
P1 | Confidence: High
- The PR updates lucide-react-native from 0.462.0 to 0.577.0, a significant version jump. This is likely a breaking change that could introduce runtime issues. The related_context shows this package is actively used via a custom wrapper. While the wrapper abstracts some usage, the underlying icon library's API or behavior may have changed. The commit log includes breaking changes like renaming icons. If the codebase uses any renamed icons, they will fail to render at runtime.
- Speculative: The changelog indicates breaking changes, including the removal of the icons namespace export. This could affect the codebase's icon import strategy if it relies on the old pattern. Without seeing the exact import statements, this risk is speculative but warrants verification.
- The version bump creates a significant version mismatch between lucide-react and lucide-react-native. This increases the risk of subtle behavioral differences between web and native platforms, potentially leading to platform-specific UI bugs.
- Speculative: The CI status includes SonarCloud Analysis in progress. A major version bump should trigger visual regression tests and snapshot updates. The absence of test file changes suggests that icon snapshot tests may fail.
Bumps lucide-react-native from 0.462.0 to 0.577.0.
Release notes
Sourced from lucide-react-native's releases.
... (truncated)
Commits
f6c0d06chore(deps): bump rollup from 4.53.3 to 4.59.0 (#4106)67c0485feat(scripts): added helper script to automatically update OpenCollective bac...b6ed43dfeat(packages): Added aria-hidden fallback for decorative icons to all packag...7a68e10fix(lucide-react-native): remove icons namespace export to enable tree-shakin...a4531a9fix(react-native-web): only add className prop to parent Icon component (#3892)076e0bbchore(dependencies): Update dependencies (#3809)1cfb3ffchore(deps-dev): bump vite from 6.3.5 to 6.3.6 (#3611)3e644fdchore(scripts): Refactor scripts to typescript (#3316)19fa01bbuild(deps-dev): bump vite from 6.3.2 to 6.3.4 (#3181)3ad1f07fix(lucide-react-native): support react 19 (#2951) (#3126)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for lucide-react-native since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)