chore(deps): update dependency happy-dom to v20.0.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
happy-dom	20.0.2 -> 20.0.11

---

Release Notes

capricorn86/happy-dom (happy-dom)

v20.0.11

Compare Source

v20.0.10

Compare Source

v20.0.9

Compare Source

v20.0.8

Compare Source

👷‍♂️ Patch fixes

• Fixes issue where previousSibling() and nextSibling() didn't work in HTMLSelectElement and HTMLFormElement - By @​capricorn86 in task #​1939
• Fixes issue where parsing an item without a permitted parent (e.g. <tr>) should be valid inside a <template> element - By @​capricorn86 in task #​1939

v20.0.7

Compare Source

👷‍♂️ Patch fixes

• Fix incorrect handling of >= operator in media query parser - By @​lkritsimas in task #​1869

v20.0.6

Compare Source

👷‍♂️ Patch fixes

• Changes implementation for DOMTokenList.forEach(), Headers.forEach() and NodeList.forEach() to be spec compliant - By @​ikeyan in task #​1858

v20.0.5

Compare Source

👷‍♂️ Patch fixes

• The setter TreeWalker.currentNode should validate if the value is a Node - By @​capricorn86 in task #​1935

v20.0.4

Compare Source

👷‍♂️ Patch fixes

• Only adds buttons to FormData if they are the submitter - By @​maxmil and @​
  karpiuMG in task #​1859

v20.0.3

Compare Source

👷‍♂️ Patch fixes

• Moves URL resolution to after checking if module preloading is enabled to prevent URL errors to be thrown when unresolvable - By @​iam-medvedev in task #​1851
• Fixes issue where CSS variables aren't parsed correctly when inside CSS functions - By @​fimion in task #​1837

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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.

---

Summary by cubic

Upgrade happy-dom from 20.0.2 to 20.0.11 to improve our test DOM environment with patch fixes and better spec compliance.
Notable fixes include correct forEach iteration, media query >= parsing, FormData submit button handling, CSS variables in functions, valid template parsing (e.g., ), and sibling navigation in select/form elements.

^{Written for commit 661ebfd. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
react-email	Ready	Preview, Comment	Jan 8, 2026 1:33pm
react-email-demo	Ready	Preview, Comment	Jan 8, 2026 1:33pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 661ebfd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cubic-dev-ai]

No issues found across 2 files

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​next/​env@​15.3.1
	@​radix-ui/​react-toggle@​1.1.10
	@​radix-ui/​react-slot@​1.2.3
	@​radix-ui/​react-collapsible@​1.1.12
	@​radix-ui/​react-toggle-group@​1.1.11
	@​radix-ui/​react-tabs@​1.1.13
	@​radix-ui/​react-dropdown-menu@​2.1.16
	@​radix-ui/​react-popover@​1.1.15
	@​radix-ui/​react-tooltip@​1.2.8
	@​radix-ui/​react-tabs@​1.1.2
	@​radix-ui/​react-select@​2.2.6
	@​types/​babel__core@​7.20.5
	@​types/​css-tree@​2.3.11
	normalize-path@​3.0.0
	@​types/​babel__traverse@​7.20.7
	prompts@​2.4.2
	@​responsive-email/​react-email@​0.0.4
	@​radix-ui/​colors@​3.0.0
	punycode@​2.3.1
	postcss@​8.4.31 ⏵ 8.5.6	+1		+1
	vite@​6.4.1
	commander@​13.1.0
	@​react-email/​tailwind@​1.0.4 ⏵ 0.0.12	+2		-8	-1
	@​react-three/​drei@​9.122.0
	@​lottiefiles/​dotlottie-react@​0.13.3
	@​react-three/​fiber@​9.4.2
	@​react-email/​tailwind@​1.0.4 ⏵ 0.0.17	+2		+1	+2
	@​tailwindcss/​postcss@​4.1.17
	@​supabase/​supabase-js@​2.49.4

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm vite is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: packages/tailwind/integrations/vite/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report