Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 5, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/browser (source) ^3.2.4 -> ^4.0.0 age adoption passing confidence
@vitest/ui (source) ^3.2.4 -> ^4.0.0 age adoption passing confidence
happy-dom ^18.0.1 -> ^20.0.0 age adoption passing confidence
recharts ^2.12.6 -> ^3.0.0 age adoption passing confidence
vitest (source) ^3.2.4 -> ^4.0.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/browser)

v4.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.0

Compare Source

Vitest 4.0 is out!

To stay updated, read our blog post and check the migration guide.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
capricorn86/happy-dom (happy-dom)

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

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

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

v20.0.2

Compare Source

👷‍♂️ Patch fixes

v20.0.1

Compare Source

👷‍♂️ Patch fixes
  • Adds warning for environment with unfrozen intrinsics (builtins) when JavaScript evaluation is enabled- By @​capricorn86 in task #​1932
    • A security advisory has been reported showing that the recommended preventive measure of running Node.js with --disallow-code-generation-from-strings wasn't enough to protect against attackers escaping the VM context and accessing process-level functions. Big thanks to @​cristianstaicu for reporting this!
    • The documentation for how to run Happy DOM with JavaScript evaluation enabled in a safer way has been updated. Read more about it in the Wiki

v20.0.0

Compare Source

I avoid making breaking changes as much as possible in Happy DOM. When I have to make a breaking change, I try to keep it as minimal as possible. This could be a breaking change that impacts many projects, and I am truly sorry if you are negatively affected by this.

💣 Breaking Changes
  • Due to security risks, JavaScript evaluation is now disabled by default - By @​capricorn86 in task #​1930
    • A security advisory (GHSA-37j7-fg3j-429f) has been reported that shows a security vulnerability where it's possible to escape the VM context and get access to process level functionality. Big thanks to @​Mas0nShi for reporting this!
    • Due to this security risk, JavaScript evaluation is now disabled by default to prevent that consumers accidentally executes untrusted code without taking precautions
    • JavaScript evaluation can be enabled by setting enableJavaScriptEvaluation to "true". Read more about how to enable this in a safer way in the Wiki

[v19.0.2](ht


Configuration

📅 Schedule: Branch creation - "before 9am on monday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 force-pushed the renovate/major-npm-packages branch 2 times, most recently from e884508 to 561c174 Compare October 12, 2025 16:55
@renovate renovate bot force-pushed the renovate/major-npm-packages branch from 561c174 to 46e31bf Compare October 19, 2025 17:08
@renovate renovate bot force-pushed the renovate/major-npm-packages branch from 46e31bf to a2e492c Compare October 26, 2025 17:10
@renovate
Copy link
Contributor Author

renovate bot commented Oct 26, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 5 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
 ERR_PNPM_FETCH_401  GET https://npm.pkg.github.com/@voidzero-dev%2Fvite-plus: Unauthorized - 401

This error happened while installing a direct dependency of /tmp/renovate/repos/github/voidzero-dev/vibe-dashboard

An authorization header was used: Bearer ghp_[hidden]

These authorization settings were found:
@jsr:registry=https://npm.jsr.io/
@voidzero-dev:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:_authToken=ghp_[hidden]

@Boshen Boshen merged commit 5c08ddb into main Oct 27, 2025
0 of 4 checks passed
@Boshen Boshen deleted the renovate/major-npm-packages branch October 27, 2025 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant