chore(deps): bump lucide-react from 1.18.0 to 1.21.0#48
Merged
Conversation
Bumps [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) from 1.18.0 to 1.21.0. - [Release notes](https://github.com/lucide-icons/lucide/releases) - [Commits](https://github.com/lucide-icons/lucide/commits/1.21.0/packages/lucide-react) --- updated-dependencies: - dependency-name: lucide-react dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
BigSimmo
pushed a commit
that referenced
this pull request
Jul 20, 2026
…amps CodeRabbit review findings on #1009, verified against the live run history: 2026-07-20 is a Monday, and the 'dropped Sunday fire' never happened - the Sunday 2026-07-19 slot fired as scheduled run #48 (19:03 UTC, success), and Monday has no slot since #923 moved the cron from daily to weekly. Rewrote the workflow comment, ledger row, and db-maintenance cross-reference to the truth (the probe stands as proactive hardening for the weekly cadence). Probe now measures staleness from updated_at (~completion time; payload has no completed_at) with a finite-timestamp guard instead of run_started_at. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EXsJcLrbZUXwnBeG91cVo9
12 tasks
BigSimmo
added a commit
that referenced
this pull request
Jul 20, 2026
…(DB easy wins) (#1009) * feat(ops): eval-canary liveness probe + database advisor triage docs - ci.yml static-pr gains a warn-only canary-staleness step (read-only actions:read job permission): GitHub cron fires are best-effort — the 2026-07-20 Sunday 18:00 slot silently never ran and nothing noticed. PR traffic now surfaces a >8-day canary drought within hours; API errors degrade to a warning, never a failure - docs/db-maintenance.md (new): 2026-07-20 Supabase advisor snapshot with standing dispositions — security clean by design (document_title_words RLS-no-policy = the deliberate fail-closed service-role-only pattern, recorded here; schema comment skipped to avoid drift-manifest churn); ~33 unused-index INFOs recorded as a TRIAGE list (retrieval-surface trgm indexes flagged RAG-protected, owner-scoped indexes kept for the multi-tenant design, operational candidates deferred); auth connection-strategy note; telemetry-retention decision recorded as open (purge:query-logs exists, deliberately unscheduled pending explicit policy) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EXsJcLrbZUXwnBeG91cVo9 * fix(ci): correct canary-drop narrative + harden liveness probe timestamps CodeRabbit review findings on #1009, verified against the live run history: 2026-07-20 is a Monday, and the 'dropped Sunday fire' never happened - the Sunday 2026-07-19 slot fired as scheduled run #48 (19:03 UTC, success), and Monday has no slot since #923 moved the cron from daily to weekly. Rewrote the workflow comment, ledger row, and db-maintenance cross-reference to the truth (the probe stands as proactive hardening for the weekly cadence). Probe now measures staleness from updated_at (~completion time; payload has no completed_at) with a finite-timestamp guard instead of run_started_at. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EXsJcLrbZUXwnBeG91cVo9 --------- Co-authored-by: Claude <noreply@anthropic.com>
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 1.18.0 to 1.21.0.
Release notes
Sourced from lucide-react's releases.
... (truncated)
Commits
5ff536eci(release.yml): Fix workflow and removeversionscripts in package scripts...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)