Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

renovate wants to merge 1 commit into from

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.563.0 age confidence

Release Notes

lucide-icons/lucide (lucide-react)

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

v0.534.0: Version 0.534.0

Compare Source

What's Changed

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

v0.533.0: Version 0.533.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.532.0...0.533.0

v0.532.0: Version 0.532.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.531.0...0.532.0

v0.531.0: Version 0.531.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.530.0...0.531.0

v0.530.0: Version 0.530.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.529.0...0.530.0

v0.529.0: Version 0.529.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.528.0...0.529.0

v0.528.0: Version 0.528.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.527.0...0.528.0

v0.527.0: Version 0.527.0

Compare Source

What's Changed

Full Changelog: lucide-icons/lucide@0.526.0...0.527.0

v0.526.0: Version 0.526.0

Compare Source

What's Changed

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 resources showing infrequent updates with only 1 event/week for the last 6 weeks, which is unusual compared to typical patterns.
Policies 🔴 ▃▂▁ Multiple S3 buckets and security groups are showing unusual policy violations, including missing tags and lack of server-side encryption, which may need review.

View signals ↗

🔥 Risks

Tip

✔ All risks disproven

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

🧠 Reasoning · ✖ 3 · ✔ 0

EC2 AMI/instance replacement affecting networking and EBS volumes

Observations 3

Hypothesis

Replacing the EC2 instance’s AMI from ami-00bfb270010738482 to ami-035c2af7e184302d8 can change the OS, kernel, and drivers, which may affect compatibility with existing ENIs, EIPs, DNS expectations, and attached EBS volumes. Instance replacement or recreation can modify ENI and IP attachments, potentially causing downtime, IP reassignment, or mismatch with existing network configuration. Attached EBS volumes such as vol-0e2b4296b2bd81424 may be detached or deleted if DeleteOnTermination is set on root or data volumes, risking data loss and service interruption during or after the replacement.

Investigation

What’s actually changing is clear in the plan: the EC2 instance (540044833068.eu-west-2.ec2-instance.i-06454595ec548264a) will be replaced solely due to the AMI change, and Terraform also includes an update to the Elastic IP resource (540044833068.eu-west-2.ec2-address.13.134.236.98) and a replacement of the load balancer target group attachment (github.com/overmindtech/terraform-example.aws_lb_target_group_attachment.module.api_access[0].aws_lb_target_group_attachment.api_server_ip). This indicates the plan already re-associates the EIP and re-registers the target with the LB as part of the cutover, rather than leaving them mismatched.

From current state, the instance’s primary ENI (eni-020b762e197effb8a) carries the EIP 13.134.236.98 and private IP 10.0.101.48; the only attached volume is the root gp3 volume vol-0e2b4296b2bd81424 with DeleteOnTermination=true. AWS documentation confirms the default behavior is to delete the root volume on instance termination, while non-root volumes are preserved by default; in this case there are no additional data volumes attached, so the hypothesis’ data‑loss claim isn’t substantiated by evidence. (docs.aws.amazon.com)

EIP behavior is also well understood and documented: it can be disassociated and rapidly re-associated to the new instance/ENI; AWS notes you should expect connections to be closed during re-mapping, but this is exactly what the plan accounts for by updating the EIP resource. There is no sign that the EIP will change or be released; the address itself remains 13.134.236.98. (docs.aws.amazon.com)

Finally, while AMI swaps can imply OS/kernel/driver differences, there’s no concrete evidence here of ENA/NVMe incompatibilities or other configuration mismatches. The instance type remains t4g.nano and the networking, VPC, subnets, and security groups are unchanged. Without proof of an incompatible AMI architecture or missing drivers, and given the coordinated updates to EIP and LB target attachment, this reads as a routine instance replacement with expected, brief cutover rather than a concrete risk of misconfiguration, IP drift, or data loss. If zero downtime is required, that would hinge on deployment strategy (e.g., multiple targets, create_before_destroy, deregistration delay), which is outside the hypothesis’ claim and not evidenced here. (docs.aws.amazon.com)

✖ Hypothesis disproven

EIP association/reassociation risk to external connectivity

Observations 8

Hypothesis

Elastic IP 13.134.236.98, associated with ENI eni-020b762e197effb8a and EC2 instance i-06454595ec548264a (private IP 10.0.101.48), is being updated with an empty diff but status “updated”. Any reassociation, disassociation, or allocation change of this EIP can alter external reachability of the ENI and instance, disrupting inbound client traffic, breaking connectivity for services that rely on this public address, and impacting routing. Within VPC vpc-02901bcbb89561298, reassignment of this or related EIPs (for example, eni-030542fb12761bd4f with 52.56.230.253) can change routing/NAT behavior and impact multiple instances that depend on these static mappings. Changes may cause downtime until consumers, routing configurations, and any public DNS records are updated to reflect the new association.

Investigation

I checked the planned changes and only three resources are in scope: the Elastic IP 540044833068.eu-west-2.ec2-address.13.134.236.98 (marked updated with an empty diff), the EC2 instance 540044833068.eu-west-2.ec2-instance.i-06454595ec548264a (REPLACED due to AMI change), and a target group attachment (also replaced with no visible attribute diff). No NAT gateways or other EIPs are being modified in this plan.

In the current state, EIP 13.134.236.98 is associated to ENI eni-020b762e197effb8a on instance i-06454595ec548264a (private 10.0.101.48). The NAT gateway’s EIP 52.56.230.253 is associated to a different ENI (eni-030542fb12761bd4f) for a NAT gateway and is unrelated to the instance EIP. There is no evidence that the NAT EIP or routing tables are changing.

AWS documentation confirms an Elastic IP can be associated with either an instance or a network interface and can be disassociated/re-associated without changing the public IP itself; remapping changes the target resource but retains the same external IP. Therefore, consumers or DNS records that point at 13.134.236.98 would not need updating if Terraform re-associates the EIP to the replacement instance. The claim that DNS or routing must be updated due to this change is not supported. Any brief interruption during instance replacement and EIP remapping would be the normal, transient behavior of a single-instance replacement rather than a distinct misconfiguration risk, and the hypothesis’ extension to NAT behavior and “multiple instances” impact is outside the actual planned changes. (docs.aws.amazon.com)

✖ Hypothesis disproven

Stale DNS and ELB target health due to EIP or IP changes

Observations 9

Hypothesis

Elastic IP 13.134.236.98 fronts ENI eni-020b762e197effb8a (private IP 10.0.101.48), which is registered as a target in an ELB target group (e.g., api-health-terraform-example on TCP:9090) and is referenced via DNS names such as ec2-13-134-236-98.eu-west-2.compute.amazonaws.com. Any change to the EIP allocation or association, or to the instance/ENI/IP behind it, can stale DNS A records pointing at 13.134.236.98 and break load balancer target health, causing targets to appear unhealthy and client traffic or health checks to fail until DNS and ELB target configuration are updated. When EC2 instance i-06454595ec548264a is replaced (AMI change), the primary private IP 10.0.101.48 and its ENI can be detached, recreated, or reassigned, making ELB/NLB targets that reference 10.0.101.48:9090 (such as the api-health-terraform-example target group) point to a non-existent or unhealthy endpoint. This can cause load balancer routing disruption and downtime unless targets are drained, re-registered to the new IP/ENI, and monitored for health during the replacement.

Investigation

Claim: replacing EC2 i-06454595ec548264a and possible EIP/ENI/IP changes will leave DNS and the NLB target group stale, causing unhealthy targets and downtime.

Evidence from the plan and current state does not support this. The EIP 13.134.236.98 resource shows an update with no diff, and in the current state it is associated to ENI eni-020b762e197effb8a on 10.0.101.48 for the instance. Elastic IPs are static and can be re-associated to a new instance/ENI without changing the public address or its AWS-provided DNS name; reassociation is an idempotent API operation, so no persistent "stale DNS" occurs so long as the EIP itself is retained. (docs.aws.amazon.com)

The NLB target group api-health-terraform-example is target type ip on TCP:9090 and currently has 10.0.101.48:9090 healthy. With ip target groups you register IP addresses explicitly; if a backend IP changes you must update the registration. The plan already includes replacement of the aws_lb_target_group_attachment.api_server_ip resource, which is exactly what re-registers the target IP, indicating the change accounts for a new private IP on replacement. (docs.aws.amazon.com)

While a very brief health flap could occur during replacement if there is only a single target, the hypothesis asserts sustained stale DNS and target configuration. Given the static EIP and the explicit re-registration of the target attachment in this change, there is no strong evidence that DNS or ELB target health will remain stale or cause downtime.

✖ Hypothesis disproven

💥 Blast Radius

Items 46

Edges 188

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 ↗

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