build(deps): bump lucide-react from 0.468.0 to 1.25.0 in /apps/wails/frontend - #397
Conversation
Bumps [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) from 0.468.0 to 1.25.0. - [Release notes](https://github.com/lucide-icons/lucide/releases) - [Commits](https://github.com/lucide-icons/lucide/commits/1.25.0/packages/lucide-react) --- updated-dependencies: - dependency-name: lucide-react dependency-version: 1.25.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce8d000af3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "date-fns": "^4.4.0", | ||
| "dayjs": "^1.11.21", | ||
| "lucide-react": "^0.468.0", | ||
| "lucide-react": "^1.25.0", |
There was a problem hiding this comment.
Commit the workspace lockfile update
This bumps the workspace dependency range, but the root package-lock.json still records apps/wails/frontend with lucide-react: ^0.468.0 and resolves node_modules/lucide-react to 0.468.0. I checked the Wails frontend CI/release paths: .github/workflows/ci.yml installs with npm ci before npm --prefix apps/wails/frontend run build, and .github/workflows/release.yml also runs npm ci; npm's bundled npm-ci docs state it exits with an error when the lockfile dependencies do not match package.json instead of updating the lock. Please regenerate and commit package-lock.json with this dependency bump so those installs can proceed deterministically.
Useful? React with 👍 / 👎.
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps lucide-react from 0.468.0 to 1.25.0.
Release notes
Sourced from lucide-react's releases.
... (truncated)
Commits
f229f83chore(depedencies): Update dependencies (#4553)5ff536eci(release.yml): Fix workflow and removeversionscripts in package scripts...07c885efix(docs): fix zephyr-cloud URL in readmes50d8af5docs(readme): Update readme files (#4320)653e44bfeat(packages): use .mjs for ESM bundles (#4285)7623e23feat(docs): add Zephyr Cloud to Hero Backers tier & rework updateSponsors scr...dada0a8fix(lucide-react): Fix dynamic imports (#4210)a6e648afix(lucide-react): correct client directives in RSC files (#4189)1f010a3fix(lucide-react): Fixes provider export and RSC render issues (#4175)484f2c9docs(version-1): Version 1 website (#4142)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for lucide-react 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)