Skip to content

chore(deps): bump lucide-react from 0.562.0 to 0.575.0 #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump lucide-react from 0.562.0 to 0.575.0 #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/web-tanstack/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"clsx": "^2.1.1",
"convex": "^1.31.7",
"framer-motion": "^12.29.0",
"lucide-react": "^0.562.0",
"lucide-react": "^0.575.0",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update bun.lock for lucide-react version bump

This dependency change updates apps/web/package.json but leaves bun.lock pinned to lucide-react@0.562.0 (both the workspace dependency entry and resolved package entry), which makes the lockfile inconsistent with the manifest. I checked .github/workflows/ci.yml and multiple jobs run bun install --frozen-lockfile; per bun install --help, that flag "Disallow[s] changes to lockfile", so these installs will fail whenever they need the lockfile to reflect this new range.

Useful? React with 👍 / 👎.

"posthog-js": "^1.347.2",
"react": "^19.0.0",
"react-dom": "^19.0.0",
Expand Down
Loading