chore(deps): update tailwind css to v0.5.20

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@tailwindcss/typography	0.5.19 → 0.5.20

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

tailwindlabs/tailwindcss-typography (@​tailwindcss/typography)

v0.5.20

Compare Source

Fixed

• Support installing with stable versions of Tailwind CSS v4 (#​424)

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • "before 10am on friday"
• 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.

[github-actions]

Caution

[High Risk] Replacing the directly internet-exposed EC2 endpoint will interrupt public access and preserves a non-compliant public EC2 design

The change replaces the public API instance behind Elastic IP 13.134.236.98, and that address is directly attached to the instance ENI rather than fronted by a load balancer or WAF. Current state shows 540044833068.eu-west-2.ec2-instance.i-08370f7d3e016a56a is serving internet traffic on 443 through security group sg-03cf38efd953aa056, which violates the organization’s requirement that EC2 instances must not be directly reachable from the internet and matches the AWS guidance against using public EC2 instances as direct endpoints.

Because the instance is being replaced, the EIP association will be reattached during apply. With no managed public edge in front of it, that cutover will interrupt direct traffic to 13.134.236.98, and the service remains exposed as a raw EC2 endpoint after the change. The internal NLB health target on 10.0.101.219:9090 is based on the private IP, so the main risk is direct public endpoint disruption and continued policy-violating exposure, not the internal target group losing its EIP mapping.
_{View reasoning tree here.}

Signals

Routine → Multiple API server resources showing unusual update patterns that may need review, with most resources at 1 event/week for the last 3 months, and related resources at 1 event/week for the last 4 months and 1 event/week for the last 5 months.

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