feat(deps): update dependency lucide-react (1.55.0 → 1.56.0)

[its-miso]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lucide-react (source)	1.55.0 → 1.56.0

---

Release Notes

lucide-icons/lucide (lucide-react)

v1.56.0: Version 1.56.0

Compare Source

What's Changed

• feat(icons): added server-nas icon by @​benhaube in #​4537
• fix(icons,categories): fix notifications category name and refine circle-x tags by @​Rachit315 in #​4994
• feat(icons): add message-circle-text icon by @​ericfennis in #​4898

New Contributors

• @​Rachit315 made their first contribution in #​4994

Full Changelog: lucide-icons/lucide@1.55.0...1.56.0

---

Configuration

📅 Schedule: (in timezone America/Edmonton)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3 (anthropic) — primary route · pr-reviewer-action v3.4.1

Recommendation: Approve

This is a Renovate-generated dependency bump of lucide-react from 1.55.0 to 1.56.0. The diff touches only package-lock.json, and the changes are confined to the version / resolved / integrity fields within the single node_modules/lucide-react block. No source files, package.json, config, or other dependency entries change. CI is fully green (build, lint, typecheck, tests, docker builds, npm audit).

Change-by-change findings

package-lock.json — node_modules/lucide-react block (lines 8392–8394)

Three lines change, exactly matching the diff: the version moves from 1.55.0 to 1.56.0, and the resolved/integrity hashes update in lockstep. The license field and peerDependencies block (which pins @types/react and react) are unchanged. package.json still declares "lucide-react": "^1.0.0", so the caret range accepts 1.56.0 without a manifest edit.

Upstream lucide-react@1.56.0 (release notes verified)

The 1.56.0 release notes describe three commits, all additive and isolation-tested against the consumer API:

• a new icon server-nas (new icon name; nothing the codebase imports)
• a fix to the notifications category title (no consumer-facing API change)
• a new icon message-circle-text (new icon name; nothing the codebase imports)

This is a low-risk minor bump — purely icon additions and a docs/category fix. No removals, deprecations, peer-dependency changes, or signature changes. The package's peerDependencies on react and @types/react are unchanged.

Local lucide-react imports

The codebase imports the following names from lucide-react across automation UI pages and shared components: ExternalLink, RefreshCw, GitBranch, AlertTriangle, CheckCircle, XCircle, Clock, Trash2, PauseCircle, ArrowLeft, Play, Loader2, AlertCircle, CheckCircle2, Hash, MessageSquareWarning, GitPullRequest, MessageSquare, MoreVertical, User, Users, X, Scissors, Info, Ban, Moon, Sun. None of these are the new server-nas or message-circle-text icons, and none were renamed or removed in 1.56.0. All previously imported icons remain available — no call-site changes are needed.

Claims to Falsify

Claim 1 — Single package, version-only bump

"Diff the PR against main and confirm exactly one block (node_modules/lucide-react) was modified and only the version/resolved/integrity fields within that block changed; no other node_modules blocks, top-level package.json, or source files were touched."

• Scope item: package-lock.json:lucide-react — held: 1/1. The diff shows exactly three changed lines, all within the node_modules/lucide-react block, restricted to version, resolved, integrity. No other node_modules/* block differs.

Claim 2 — No other files changed

"Compute a diff vs main and verify only the three lines under node_modules/lucide-react (version, resolved, integrity) change and every other file is unchanged."

• Scope items: package.json (held), package-lock.json other than lucide-react entry (held; only the named three lines move), all application source files (held; git_diff_name_only returned empty for additional files, and the changed-files count is 1). Repository history confirms 6572c06 is the only commit on the branch.

Both claims held.

Standards Compliance

The repository standards document bundled with the corpus (AGENTS.md-derived) calls out lint/typecheck gating, secret handling, and CI conventions. This PR touches none of those axes — it updates only a lockfile entry, and lint/typecheck/tests/docker builds all pass in CI.

No repository standard is violated.

Tool Harness Findings

The harness executed the verification plan: a git_diff_* pair confirming the diff is a single file (package-lock.json), package.json and read_file confirming the caret range is unchanged, git_grep enumerating every lucide-react import site (none affected), and web_fetch against the upstream 1.56.0 release page (confirmed release notes and that 1.56.0 exists). No harness finding is unresolved.

Sources

• Repo files inspected: package.json, package-lock.json (diff line range 8391–8396), AGENTS.md.
• Upstream verified: https://github.com/lucide-icons/lucide/releases/tag/1.56.0 and the lucide-icons/lucide@1.55.0...1.56.0 compare, both confirming the release is a 3-commit additive bump (two new icons + a category/docs fix), published 2026-10-13.
• CI evidence: all 11 listed checks pass (Build, Typecheck, Tests, Lint, Coverage, npm audit, Docker Build, Docker Build (MCP), smoke, Workflow lint, Database migrations, Database integration).

Required Check Dispositions

• "check for breaking API changes in updated dependencies" — satisfied: only lucide-react is bumped (1.55.0 → 1.56.0), and the release notes show no removed/renamed exports or peer-dependency changes; every name this codebase imports from lucide-react remains available.
• "run full test suite after upgrade" — satisfied: CI test/check/coverage jobs are all green on the head commit.

Unknowns / Needs Verification

None. The change surface is one lockfile block with no manifest edit, no source edit, and no behavior change. The upstream release page is corroborating but not strictly required for verification of an additive icon bump — even with the fetch as partial HTML, the structured release/compare metadata in the corpus confirms three additive commits and no removals.