chore: Bump lucide-react from 0.545.0 to 1.17.0#2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) from 0.545.0 to 1.17.0. - [Release notes](https://github.com/lucide-icons/lucide/releases) - [Commits](https://github.com/lucide-icons/lucide/commits/1.17.0/packages/lucide-react) --- updated-dependencies: - dependency-name: lucide-react dependency-version: 1.17.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
InstaZDLL
added a commit
that referenced
this pull request
May 30, 2026
Absorbs the eight dependabot major-version PRs (#2-#10) into this branch so the bootstrap state is on the latest of every dep we ship. Closing the standalone bot PRs in favour of this one keeps the review surface single. Bumps (all major): - lucide-react 0.545 -> 1.17 (default import API unchanged; no call site adjustments needed) - eslint-plugin-react-hooks 5 -> 7 (new `set-state-in-effect` rule fires on ThemeToggle's mount-time setState — fixed by switching to lazy initial state instead of effect-driven init) - @commitlint/cli + config-conventional 19 -> 21 (no rule change needed; existing .commitlintrc.cjs stays compatible) - globals 15 -> 17 (additive — browser/node entries unchanged) - @types/node 22 -> 25 (type defs only; tsc clean) - jsdom 28 -> 29 (vitest env; no test files yet so no behaviour surface to break) Held back (with rationale): - eslint 9 -> 10 + @eslint/js 9 -> 10: eslint-plugin-react still caps at peer ^9.7 and throws `contextOrFilename.getFilename is not a function` under v10. Reverting to v9 until eslint-plugin-react ships v10 support — re-enable when upstream catches up. ThemeToggle refactor: - Mount-time `setMode(getInitialMode())` inside useEffect was the scaffold pattern; v7's react-hooks/set-state-in-effect rule correctly flags it. Now `useState(getInitialMode)` is the lazy initialiser, the useEffect only calls applyThemeMode (which must stay in an effect because it touches `document` and would break SSR otherwise). exhaustive-deps disabled on that effect with rationale. Validated: - bun run format:check OK - bun run lint OK - bun run typecheck OK - bun run build OK - bun run test OK (no test files; passWithNoTests carry-over from the previous commit) Signed-off-by: InstaZDLL <github.105mh@8shield.net>
Contributor
Author
|
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. |
This was referenced May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps lucide-react from 0.545.0 to 1.17.0.
Release notes
Sourced from lucide-react's releases.
... (truncated)
Commits
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)a0e202dfeat(packages/angular): add new@lucide/angularpackage (#3897)c5b155eMerge branch 'main' of https://github.com/lucide-icons/lucide into nextMaintainer 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)