Skip to content

Update dependency eslint-plugin-react-refresh to v0.5.8 - #557

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/prettier-npm
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/prettier-npm

Conversation

@renovate

@renovate renovate Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-react-refresh 0.5.3 → 0.5.8 age confidence

Release Notes

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

v0.5.8

Compare Source

  • Handle more cases in export default declaration (fixes #​119)

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.

@renovate renovate Bot added dependencies Renovatebot and dependabot updates frontend javascript Pull requests that update javascript code labels Oct 8, 2026
@renovate
renovate Bot enabled auto-merge (squash) October 8, 2026 23:29
@github-actions

github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Caution

[High Risk] Single backend replacement will leave the ALB and txn-feed NLB with no healthy targets during cutover

This change replaces the only healthy backend behind two live AWS load-balanced paths. The ALB target group api-207c90ee-tg currently has a single healthy instance target on HTTP port 80 (/health), and that instance 540044833068.eu-west-2.ec2-instance.i-0bf4039822e01f430 is being replaced because its ami changes. At the same time, the corresponding aws_lb_target_group_attachment resource is also replaced. During apply, the old target can be deregistered before the new instance is registered and healthy, leaving the public API ALB with no healthy targets and causing 5xx responses.

The internal transaction feed path has the same failure mode and even less redundancy. The NLB target group txn-feed-terraform-example currently has exactly one healthy IP target, 10.0.101.34:9090, which belongs to the separately replaced core-api instance 540044833068.eu-west-2.ec2-instance.i-0cff13d553da3fe3a. Because that instance and its attachment are both being replaced, any cutover delay or startup failure leaves the listener with no healthy forwarding destination on port 9090. That will interrupt transaction delivery to the feed endpoint and can break downstream processing continuity.
View reasoning tree here.

Warning

[Medium Risk] EC2 replacement will invalidate current instance IPs and EC2-generated hostnames

The EC2 replacements for 540044833068.eu-west-2.ec2-instance.i-0bf4039822e01f430 and 540044833068.eu-west-2.ec2-instance.i-07f8673d7f075bf4b will change their primary ENIs and auto-assigned network identities. The current API server is attached to eni-0ff298661a77e3920 with private IP 10.0.101.252 and public IP 13.40.73.249, and the fraud processor is attached to eni-0b505b8612079c014 with private IP 10.50.101.95. In both diffs those fields become (known after apply), and there is no preserved ENI or fixed private IP configured for the replacement.

After apply, any callers, scripts, DNS records, or routing references that talk directly to those instance-specific IPs or EC2-generated hostnames will point at dead identities. The ALB target attachment and the separate Elastic IP on 13.134.236.98 appear to be updated correctly, so the risk is narrower than the hypothesis suggests, but direct consumers of the replaced instances' existing network identities will lose connectivity until they are updated.
View reasoning tree here.

Signals

Routine → Multiple compute and monitoring resources showing unusual routine changes at 1 event/week for the last 2-5 months, with an email subscription resource at 2 events/week for the last 5 months and several API server resources at 3-4 events/week for the last 3-5 months, which is infrequent compared to typical patterns.

Additional Change Details: Items 101 Edges 177 model|risks_v6 ✨Encryption Key State Risk ✨KMS Key Creation

View in Overmind

@renovate
renovate Bot force-pushed the renovate/prettier-npm branch from 10f1c1c to a13920d Compare November 16, 2026 00:07
@renovate renovate Bot changed the title Update dependency eslint-plugin-react-refresh to v0.5.7 Update dependency eslint-plugin-react-refresh to v0.5.8 Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants