Update dependency eslint-plugin-react-refresh to v0.5.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-react-refresh	0.5.3 → 0.5.7

---

Release Notes

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.7

Compare Source

Add allowCompoundComponents option (#​117)

Default: false (true in vite config)

Don't warn when components are exported as an object gathering them. Every member of the object must be a component, and a member holding an anonymous function requires a component name as key.

This should be enabled if the fast refresh implementation correctly handles this case. Vite supports it since @vitejs/plugin-react 4.7.0, @vitejs/plugin-react-swc 3.11.0.

{
  "react-refresh/only-export-components": [
    "error",
    { "allowCompoundComponents": true }
  ]
}

Enabling this option allows code such as the following:

const Root = () => <></>;
const Label = () => <></>;
export const Tag = { Root, Label };

v0.5.6

Compare Source

• Support re-exporting namespace components (fixes #​116)

v0.5.5

Compare Source

• Fix SCREAMING_SNAKE_CASE constant exported via export { Name } incorrectly treated as React component #​114 (fixes #​113)
• Add contentType and size to allowExportNames in Next config #​115

v0.5.4

Compare Source

• Add instant to allowExportNames in Next config #​112

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • "before 10am on friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.

[github-actions]

Caution

[High Risk] Single-backend target group replacement will temporarily remove healthy API targets

This change replaces the only EC2 backend behind api-207c90ee-tg and the only IP backend behind txn-feed-terraform-example, while the corresponding aws_lb_target_group_attachment resources are also being replaced. Current target health shows i-0bf4039822e01f430:80 and 10.0.101.34:9090 are each the sole healthy target in their group, so deregistering the old backend before the replacement instance has finished booting and passed health checks will leave the load balancer with no healthy target.

The recovery window is not instantaneous. The ALB target group requires two successful HTTP /health checks at 30 second intervals, and the NLB target group requires three successful TCP checks at 30 second intervals before a replacement target is considered healthy. During that interval, API traffic behind the existing listeners and public endpoints will fail or flap, and the existing Route53 and CloudWatch health alarms are likely to trigger because they already monitor these paths closely.
_{View reasoning tree here.}

Signals

Routine → Multiple compute resources showing unusual and infrequent routine changes at 1 event/week for the last 2-5 months, with additional instance resources at 3 events/week for the last 5 months, which is infrequent compared to typical patterns.

_{Additional Change Details:} Items 87 Edges 178 model|risks_v6 ✨Encryption Key State Risk ✨KMS Key Creation