Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Update Test families (major) #585

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jsdom 24.1.3 -> 25.0.0 age adoption passing confidence
vitest (source) 1.6.0 -> 2.0.5 age adoption passing confidence

Release Notes

jsdom/jsdom (jsdom)

v25.0.0

Compare Source

This major release changes the prototype of a jsdom's EventTarget.prototype to point to the Object.prototype inside the jsdom, instead of pointing to the Node.js Object.prototype. Thus, the prototype chain of Window stays entirely within the jsdom, never crossing over into the Node.js realm.

This only occurs when runScripts is set to non-default values of "dangerously" or "outside-only", as with the default value, there is no separate Object.prototype inside the jsdom.

This will likely not impact many programs, but could cause some changes in instanceof behavior, and so out of an abundance of caution, we're releasing it as a new major version.

vitest-dev/vitest (vitest)

v2.0.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.0

Compare Source

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
View changes on GitHub

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

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

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 added the renovate label Jul 12, 2024
@renovate renovate bot force-pushed the renovate/major-test-families branch 2 times, most recently from 23af4d1 to 027570c Compare July 15, 2024 14:43
@renovate renovate bot force-pushed the renovate/major-test-families branch 10 times, most recently from 316bf54 to cc68529 Compare July 26, 2024 22:27
@renovate renovate bot force-pushed the renovate/major-test-families branch 3 times, most recently from ab28c25 to cd2599f Compare August 2, 2024 18:41
@renovate renovate bot force-pushed the renovate/major-test-families branch 3 times, most recently from 7898955 to 7930d6f Compare August 16, 2024 18:10
@renovate renovate bot force-pushed the renovate/major-test-families branch 3 times, most recently from fcdda21 to deb32bf Compare August 18, 2024 01:10
@renovate renovate bot force-pushed the renovate/major-test-families branch from deb32bf to cfb0e0d Compare August 25, 2024 12:53
@renovate renovate bot changed the title ci: Update dependency vitest to v2 ci: Update Test families (major) Aug 25, 2024
@renovate renovate bot force-pushed the renovate/major-test-families branch 3 times, most recently from 10903c3 to 7a7db5c Compare August 31, 2024 19:04
@renovate renovate bot force-pushed the renovate/major-test-families branch from 7a7db5c to dacbd17 Compare September 1, 2024 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants