Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 30, 2025

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) ^3.0.9 -> ^4.0.5 age confidence
vitest (source) ^3.2.4 -> ^4.0.5 age confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v4.0.5

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.4

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

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

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

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: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 requested a review from dubzzz as a code owner October 30, 2025 18:29
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 30, 2025
@changeset-bot
Copy link

changeset-bot bot commented Oct 30, 2025

⚠️ No Changeset found

Latest commit: 5f209b2

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

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 282f967 to bf78a5d Compare October 30, 2025 21:21
@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 30, 2025

@fast-check/examples

@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@6236

@fast-check/expect-type

npm i https://pkg.pr.new/@fast-check/expect-type@6236

fast-check

npm i https://pkg.pr.new/fast-check@6236

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@6236

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@6236

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@6236

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@6236

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@6236

commit: 0b63a41

@renovate
Copy link
Contributor Author

renovate bot commented Oct 30, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

github-actions bot and others added 3 commits November 1, 2025 06:41
  Applied by GitHub Action workflow: Format PR
  Run ID: 18992869395
  Target: branch 'renovate/major-vitest-monorepo'
  Applied by GitHub Action workflow: PR PNPM Conflicts
  Run ID: 19002525802
  Target PR: 6236
dubzzz
dubzzz previously approved these changes Nov 2, 2025
@dubzzz
Copy link
Owner

dubzzz commented Nov 2, 2025

@copilot part of the test failures are linked to the error described here: https://vitest.dev/guide/migration.html#spyon-and-fn-support-constructors. could you fix them by relying on the class based mock

Copy link
Contributor

Copilot AI commented Nov 2, 2025

@dubzzz I've opened a new pull request, #6259, to work on those changes. Once the pull request is ready, I'll request review from you.

Vitest v4 no longer supports using arrow functions in
`mockImplementation` for constructors (see [migration
guide](https://vitest.dev/guide/migration.html#spyon-and-fn-support-constructors)).

## Changes

- **Worker mocks**: Changed `Worker.mockImplementation(() => ({...}))`
to class-based mocks
- **Arbitrary constructor spies**: Replaced arrow functions with
`function` keyword in `mockImplementation` calls across 25 test files
- **Scheduler mocks**: Converted `mockReturnValue` to
`mockImplementation` for `SchedulerArbitrary` and `SchedulerImplem`
constructors

## Example

```typescript
// Before (v3)
const IntegerArbitrary = vi.spyOn(IntegerArbitraryMock, 'IntegerArbitrary');
IntegerArbitrary.mockImplementation(() => instance);

// After (v4)
const IntegerArbitrary = vi.spyOn(IntegerArbitraryMock, 'IntegerArbitrary');
IntegerArbitrary.mockImplementation(function() { return instance; } as any);
```

```typescript
// Before (v3)
Worker.mockImplementation(() => ({ on, postMessage, terminate }) as any);

// After (v4)
Worker.mockImplementation(class {
  on = on;
  postMessage = postMessage;
  terminate = terminate;
} as any);
```

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/dubzzz/fast-check/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: dubzzz <[email protected]>
@github-actions
Copy link
Contributor

github-actions bot commented Nov 2, 2025

👋 A preview of the new documentation is available at: http://69075aef65a796d7a6534843--dubzzz-fast-check.netlify.app

  Applied by GitHub Action workflow: PR Format
  Run ID: 19028178794
  Target PR: 6236
  Applied by GitHub Action workflow: PR PNPM Conflicts
  Run ID: 19028200853
  Target PR: 6236
@socket-security
Copy link

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 High
Protestware or unwanted behavior: npm es5-ext

Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale

From: pnpm-lock.yamlnpm/[email protected]

ℹ Read more on: This package | This alert | What is protestware?

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: Consider that consuming this package may come along with functionality unrelated to its primary purpose.

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 High
Protestware or unwanted behavior: npm es5-ext

Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.

From: pnpm-lock.yamlnpm/[email protected]

ℹ Read more on: This package | This alert | What is protestware?

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: Consider that consuming this package may come along with functionality unrelated to its primary purpose.

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

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants