Skip to content

fix(deps): update dependency lucide-react to ^0.575.0#404

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lucide-monorepo
Open

fix(deps): update dependency lucide-react to ^0.575.0#404
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lucide-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 12, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
lucide-react (source) ^0.462.0 → ^0.575.0 age confidence

Release Notes

lucide-icons/lucide (lucide-react)

v0.575.0: Version 0.575.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.573.0...0.575.0

v0.574.0

Compare Source

v0.573.0

Compare Source

v0.572.0

Compare Source

v0.571.0: Version 0.571.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.570.0...0.571.0

v0.570.0: Version 0.570.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.569.0...0.570.0

v0.569.0: Version 0.569.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.568.0...0.569.0

v0.568.0: Version 0.568.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.567.0...0.568.0

v0.567.0: Version 0.567.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.566.0...0.567.0

v0.566.0: Version 0.566.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.565.0...0.566.0

v0.565.0: Version 0.565.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.564.0...0.565.0

v0.564.0: Version 0.564.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.563.1...0.564.0

v0.563.0: Version 0.563.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.562.0...0.563.0

v0.562.0

Compare Source

v0.561.0: Version 0.561.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.560.0...0.561.0

v0.560.0: Version 0.560.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.559.0...0.560.0

v0.559.0: Version 0.559.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.558.0...0.559.0

v0.558.0: Version 0.558.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.557.0...0.558.0

v0.557.0: Version 0.557.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.556.0...0.557.0

v0.556.0: Version 0.556.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.555.0...0.556.0

v0.555.0: Version 0.555.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.554.0...0.555.0

v0.554.0: Version 0.554.0

Compare Source

What's Changed

Breaking change

For lucide-react and lucide-solid, imports for Fingerprint icon are changed to FingerprintPattern.

Lucide React
- import { Fingerprint } from "lucide-react";
+ import { FingerprintPattern } from "lucide-react";
Lucide Solid
- import { Fingerprint } from "lucide/solid";
+ import { FingerprintPattern } from "lucide/solid";

// Or

- import Fingerprint from "lucide/solid/icons/fingerprint";
+ import FingerprintPattern from "lucide/solid/icons/fingerprint-pattern";

New Contributors

Full Changelog: lucide-icons/lucide@0.553.0...0.554.0

v0.553.0: Version 0.553.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.552.0...0.553.0

v0.552.0: Version 0.552.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.551.0...0.552.0

v0.551.0: Version 0.551.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.550.0...0.551.0

v0.550.0: Version 0.550.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.549.0...0.550.0

v0.549.0: Version 0.549.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.548.0...0.549.0

v0.548.0: Version 0.548.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.547.0...0.548.0

v0.547.0: Version 0.547.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.546.0...0.547.0

v0.546.0: Version 0.546.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.545.0...0.546.0

v0.545.0: Version 0.545.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.544.0...0.545.0

v0.544.0: Version 0.544.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.543.0...0.544.0

v0.543.0: Version 0.543.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.542.0...0.543.0

v0.542.0: Version 0.542.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.541.0...0.542.0

v0.541.0: Version 0.541.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.540.0...0.541.0

v0.540.0: Version 0.540.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.539.0...0.540.0

v0.539.0: Version 0.539.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.538.0...0.539.0

v0.538.0: Version 0.538.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.537.0...0.538.0

v0.537.0: Version 0.537.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.536.0...0.537.0

v0.536.0: Version 0.536.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.535.0...0.536.0

v0.535.0: Version 0.535.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.534.0...0.535.0

[

Configuration

📅 Schedule: Branch creation - "before 10am on friday" in timezone Europe/London, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Renovatebot and dependabot updates frontend javascript Pull requests that update javascript code labels Dec 12, 2025
@env0
Copy link

env0 bot commented Dec 12, 2025 •
edited
Loading

🚀  env0 had composed a PR Plan for environment Overmind / Terraform Example / production :

Plan: 1 to add, 1 to change, 0 to destroy.
Plan Details 
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+   create
!   update in-place

Terraform will perform the following actions:


  # module.api_access[0].aws_sns_topic_subscription.oncall_email will be created
+   resource "aws_sns_topic_subscription" "oncall_email" {
+       arn                             = (known after apply)
+       confirmation_timeout_in_minutes = 1
+       confirmation_was_authenticated  = (known after apply)
+       endpoint                        = "alerts@example.com"
+       endpoint_auto_confirms          = false
+       filter_policy_scope             = (known after apply)
+       id                              = (known after apply)
+       owner_id                        = (known after apply)
+       pending_confirmation            = (known after apply)
+       protocol                        = "email"
+       raw_message_delivery            = false
+       topic_arn                       = "arn:aws:sns:eu-west-2:540044833068:production-api-alerts"
    }

  # module.heritage[0].aws_rds_cluster.face_database will be updated in-place
!   resource "aws_rds_cluster" "face_database" {
        id                                    = "facial-recognition-terraform-example"
        tags                                  = {}
        # (46 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 1 to change, 0 to destroy.

Failed to calculate cost estimation

Full PR Plan logs on env0

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from b46edd3 to 5c0b0b3 Compare December 12, 2025 11:02
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.560.0 fix(deps): update dependency lucide-react to ^0.561.0 Dec 12, 2025
@github-actions
Copy link

github-actions bot commented Dec 12, 2025 •
edited
Loading

Open in Overmind ↗

model|risks_v6
✨Encryption Key State Risk ✨KMS Key Creation

🔴 Change Signals

Routine 🔴 ▇▅▃▂▁ AWS instance (module.api_access[0].aws_eip.api_server) showing only 1 event/week for the last 6 weeks, which is infrequent compared to typical patterns.
Policies 🔴 ▃▂▁ Multiple S3 buckets are missing server-side encryption and required tags, and several security groups allow SSH access from anywhere, which is a security risk and unusual compared to typical patterns.

View signals ↗

🔥 Risks

Tip

✔ All risks disproven

We investigated 3 potential risks across 41 resources and verified each was safe. See the investigation details below.

🧠 Reasoning · ✖ 3 · ✔ 0

Elastic IP association or routing change causing external connectivity loss

Observations 1

Hypothesis

Updating the EC2 Elastic IP address 13.134.236.98 may change which resource it is associated to or how traffic is routed to it. If the Elastic IP is re-associated (e.g., moved between instances/ENIs) or if dependent DNS records and firewall rules are not updated accordingly, services that rely on this specific public IPv4 address may experience connectivity loss or traffic misrouting, causing service disruption.

Investigation

The plan shows 540044833068.eu-west-2.ec2-address.13.134.236.98 marked as updated but with an empty diff, so there is no evidence of a reassociation target (instance/ENI) or routing attribute changing. I queried the blast radius for that EIP and it returned invalid/not found, while other public IPs in this environment are clearly associated to specific ENIs and services (e.g., 52.56.230.253 on a NAT gateway ENI, 13.42.242.250 and 18.171.127.246 on ALB ENIs, 18.175.138.98 and 18.135.28.181 on EC2 primary ENIs). None of these are 13.134.236.98, and no resource currently depends on that address in the captured state. The only other planned changes are the creation of an EC2 instance and a target group attachment, neither referencing this EIP. While AWS documentation confirms EIPs can be disassociated and re-associated across resources, this plan provides no concrete change indicating such a move for 13.134.236.98. Therefore the hypothesis is speculative and not supported by the diffs or current state. (docs.aws.amazon.com)

✖ Hypothesis disproven

Load balancer target registration and health-check misconfiguration risk

Observations 6

Hypothesis

Multiple changes affect how Application/Network Load Balancers route traffic to backend instances. New aws_lb_target_group_attachment resources registering targets on port 9090 to the target group api-health-terraform-example (and its ARN form for the internal load balancer mon-internal-terraform-example) may alter the set of healthy targets and traffic distribution. Misconfigured target_ids or incorrect ports can lead to failed health checks, target flapping, or routing traffic to unhealthy/incorrect instances. New EC2 instances (e.g., aws_instance.api_server in subnet-07b5b1fb2ba02f964 with security groups sg-03cf38efd953aa056 and sg-089e5107637083db5 and tags such as Service: core-api) may automatically become ALB targets or influence target capacity for ALBs like api-207c90ee-alb and target group api-207c90ee-tg. Additional EC2 instances created in subnet subnet-07b5b1fb2ba02f964 with security groups overlapping the ALB’s security groups and tags matching ALB/target group selection criteria can change target registration and health status, increasing target count or introducing unhealthy targets that affect CloudWatch alarms and perceived availability. Overall risk: changed backend set and health state can modify load-balancing behavior, routing, and alerting, potentially reducing availability or causing connection failures for clients relying on these load balancers.

Investigation

Claim reviewed against diffs and current state. The only backend-routing change in this plan is creation of an aws_lb_target_group_attachment that will register a target on port 9090 to the Network Load Balancer’s target group api-health-terraform-example. Current state shows that NLB listener mon-internal-terraform-example listens on TCP 9090 and forwards to that same target group, which is type ip, protocol TCP, port 9090 with TCP health checks—so the planned attachment’s port/protocol align with the target group and listener. No ALB listener, rule, or ALB target group changes are planned. The referenced CloudWatch alarm api-207c90ee-unhealthy-targets is tied to the Application Load Balancer’s target group api-207c90ee-tg (HTTP:80) and is currently OK; this plan does not modify that ALB or its target group, so the alarm and ALB routing won’t be affected by this change. Instances do not auto-register to ALB/NLB target groups; attachments are explicit (or via ASG), and no such ALB attachment is in the plan. The attachment configuration itself is valid for IP-type target groups: availability_zone supports values like "all," and when registering an IP outside the target group VPC, this parameter is expected; Terraform’s attachment resource also accepts an IP as target_id for IP-type groups. Without concrete evidence of an incorrect target_id, wrong port, or missing connectivity, there is insufficient evidence that health checks or routing will break as claimed. Overall, the hypothesis mixes unrelated ALB resources with an NLB IP attachment and remains speculative given the provided diffs and current state. (docs.aws.amazon.com)

✖ Hypothesis disproven

Subnet IP/ENI exhaustion and security group interaction risk from new EC2 instance

Observations 8

Hypothesis

Creating a new EC2 instance (aws_instance.api_server) in subnet subnet-07b5b1fb2ba02f964 with security groups sg-03cf38efd953aa056 and sg-089e5107637083db5 increases IP and ENI consumption in that subnet and may interact with existing network interfaces and gateways. Additional IP usage can push the subnet toward IP exhaustion, affecting existing ENIs such as eni-0c502e5a8c20f4df7 (used by a NAT Gateway) or ENIs associated with ALBs (e.g., eni-0e0a4c6b..., eni-0bc8f90dc9b73a304, eni-030542fb12761bd4f) and their Elastic IPs. This can cause allocation failures, routing changes, or contention for ENIs and addresses, potentially impacting ALB and NAT connectivity. Attaching multiple security groups (sg-03cf38efd953aa056, sg-089e5107637083db5 and other groups overlapping the ALB’s SGs) also introduces the risk of overlapping or conflicting firewall rules, potentially altering traffic flows to existing instances or services that depend on specific security group policies or stable IP assignments. Overall risk: subnet-level IP/ENI exhaustion, changed routing through NAT, and security-group side effects degrading connectivity for ALB-backed services and other workloads in the subnet/AZ.

Investigation

What I checked:

  • Current subnet capacity: The target subnet subnet-07b5b1fb2ba02f964 (10.0.101.0/24 in eu‑west‑2a) shows AvailableIpAddressCount: 247, meaning only 4 usable addresses are currently allocated in that /24. Adding one EC2 instance will consume at most one additional private IP and one ENI in this subnet, leaving ~246 usable IPs—orders of magnitude above any exhaustion threshold. [Blast radius evidence: 540044833068.eu-west-2.ec2-subnet.subnet-07b5b1fb2ba02f964]
  • Provider behavior and requirements: AWS subnets reserve 5 addresses per subnet and ALBs require at least eight free IPs per enabled AZ; ELB also pre‑reserves ENIs to remain operable when a subnet runs low. With 247 free IPs in this subnet, neither ALB scale-out nor NAT ENI operations are at risk. (docs.aws.amazon.com)
  • Existing critical ENIs: The NAT Gateway in this subnet uses eni-0c502e5a8c20f4df7 (10.0.101.182) and the ALB uses eni-0e0a4c6b8ada663d9 (10.0.101.128). These are stable attachments; launching an additional instance does not alter their addresses or routing. [Blast radius evidence: eni-0c502e5a8c20f4df7, eni-0e0a4c6b8ada663d9, nat-0bcff9aa2633b680e, elbv2-load-balancer.api-207c90ee-alb]
  • Routing: Public subnet route table rtb-0279ca2304acbbb97 routes 0.0.0.0/0 to the IGW; private-subnet egress to NAT is handled by a separate route table pointing to nat-019b2865124bca19d in another AZ. Creating a single instance in the public subnet does not change those routes or NAT behavior. [Blast radius evidence: rtb-0279ca2304acbbb97, rtb-0fa8d71472f3214bd]
  • Security groups: The instance will attach sg-03cf38efd953aa056 and sg-089e5107637083db5 (not present in the current blast radius snapshot), while the ALB uses sg-0ac525af0d472d9bf. Even if those instance SGs exist, SG semantics are allow‑only and additive; associating multiple SGs affects only that instance’s traffic and cannot “conflict” to change other resources’ flows. This directly contradicts the hypothesis about SG conflicts impacting ALB/NAT traffic. (docs.aws.amazon.com)

Conclusion: The hypothesis is speculative and not supported by the evidence. Subnet IP utilization is extremely low; ELB/NAT ENIs and routes are unaffected by adding one instance; and SG behavior does not produce the kind of cross‑resource interference claimed. Therefore, the risk of subnet IP/ENI exhaustion or security‑group side effects degrading ALB/NAT connectivity from this change is not real.

✖ Hypothesis disproven

💥 Blast Radius

Items 41

Edges 142

github-actions[bot]
github-actions bot approved these changes Dec 12, 2025
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

✅ Auto-Approved

🟢 Decision

Auto-approved: All safety checks passed

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 5c0b0b3 to 3a8f836 Compare December 15, 2025 05:07
github-actions[bot]
github-actions bot requested changes Dec 15, 2025
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

Routine 🟢 +1

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 3a8f836 to 3a0dfb2 Compare December 18, 2025 15:11
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.561.0 fix(deps): update dependency lucide-react to ^0.562.0 Dec 18, 2025
github-actions[bot]
github-actions bot requested changes Dec 18, 2025
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

Routine 🟢 +2

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 3a0dfb2 to e1ddfb6 Compare December 31, 2025 13:15
github-actions[bot]
github-actions bot requested changes Dec 31, 2025
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from e1ddfb6 to b1cfd97 Compare January 8, 2026 17:08
github-actions[bot]
github-actions bot requested changes Jan 8, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from b1cfd97 to 34e6028 Compare January 19, 2026 19:58
github-actions[bot]
github-actions bot requested changes Jan 19, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 34e6028 to 56d8552 Compare January 23, 2026 13:11
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.562.0 fix(deps): update dependency lucide-react to ^0.563.0 Jan 23, 2026
github-actions[bot]
github-actions bot requested changes Jan 23, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

Routine 🟢 +5

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.563.0 Update dependency lucide-react to ^0.563.0 Jan 29, 2026
@renovate renovate bot changed the title Update dependency lucide-react to ^0.563.0 fix(deps): update dependency lucide-react to ^0.563.0 Jan 29, 2026
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.563.0 Update dependency lucide-react to ^0.563.0 Jan 29, 2026
@renovate renovate bot changed the title Update dependency lucide-react to ^0.563.0 fix(deps): update dependency lucide-react to ^0.563.0 Jan 29, 2026
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.563.0 Update dependency lucide-react to ^0.563.0 Jan 29, 2026
@renovate renovate bot changed the title Update dependency lucide-react to ^0.563.0 fix(deps): update dependency lucide-react to ^0.563.0 Jan 30, 2026
@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 56d8552 to cdc861d Compare February 2, 2026 19:38
@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from cdc861d to e95e5b7 Compare February 12, 2026 17:10
github-actions[bot]
github-actions bot requested changes Feb 12, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2); Routine score (-5) is below minimum (-1)

📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

💥 Blast Radius

Items 46 · Edges 188

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from e95e5b7 to faa7730 Compare February 13, 2026 12:37
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.563.0 fix(deps): update dependency lucide-react to ^0.564.0 Feb 13, 2026
github-actions[bot]
github-actions bot requested changes Feb 13, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from faa7730 to cbc757e Compare February 17, 2026 11:41
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.564.0 fix(deps): update dependency lucide-react to ^0.571.0 Feb 17, 2026
github-actions[bot]
github-actions bot requested changes Feb 17, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from cbc757e to c5bb976 Compare February 17, 2026 13:05
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.571.0 fix(deps): update dependency lucide-react to ^0.574.0 Feb 17, 2026
github-actions[bot]
github-actions bot requested changes Feb 17, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)

📊 Signals Summary

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from c5bb976 to 1d20570 Compare February 19, 2026 14:30
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.574.0 fix(deps): update dependency lucide-react to ^0.575.0 Feb 19, 2026
github-actions[bot]
github-actions bot requested changes Feb 19, 2026
View reviewed changes
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Overmind

⛔ Auto-Blocked

🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2); Routine score (-5) is below minimum (-1)

📊 Signals Summary

Routine 🔴 -5

Policies 🔴 -3

🔥 Risks Summary

High 0 · Medium 0 · Low 0

💥 Blast Radius

Items 41 · Edges 142

View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 1d20570 to 5588dfc Compare February 26, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

dependencies Renovatebot and dependabot updates frontend javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants