Skip to content

chore(deps): update dependency vitest to v5 - #267

Open
SamuelIVX wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo
Open

chore(deps): update dependency vitest to v5#267
SamuelIVX wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@SamuelIVX

@SamuelIVX SamuelIVX commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^4.0.18 → ^5.0.0 age confidence

Release Notes

vitest-dev/vitest (vitest)

v5.0.0

Compare Source

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "every weekday"
  • 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 has been generated by Mend Renovate CLI.

@github-actions github-actions Bot added the size/M label Sep 4, 2026
@coderabbitai

coderabbitai Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: ecbb326f-693e-4ab6-b6e0-b2f97751857b

📥 Commits

Reviewing files that changed from the base of the PR and between 5688bca and 220c278.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (1)
  • GitHub Check: Deploy
⚠️ CI failures not shown inline (8)

GitHub Actions: Mutation Testing / 0_Mutation Testing.txt: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run if [ "pull_request" = "pull_request" ]; then
 �[36;1mif [ "pull_request" = "pull_request" ]; then�[0m
 �[36;1m  npx stryker run --since="origin/main"�[0m
 �[36;1melse�[0m
 �[36;1m  npx stryker run�[0m
 �[36;1mfi�[0m
 shell: /usr/bin/bash -e {0}
 ##[endgroup]
 npm warn exec The following package was not found and will be installed: stryker@1.0.1
 npm warn deprecated date-format@0.0.0: 0.x is no longer supported. Please upgrade to 4.x or higher.
 npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
 npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
 npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
 npm warn deprecated glob@5.0.15: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
 npm warn deprecated streamroller@0.4.1: 0.x is no longer supported. Please upgrade to 3.x or higher.
 npm warn deprecated istanbul@0.4.5: This module is no longer maintained, try this instead:
 npm warn deprecated   npm i nyc
 npm warn deprecated Visit https://istanbul.js.org/integrations for other alternatives.
 npm warn deprecated stryker-api@0.9.0: Stryker v1 is released, but you're still using a 0.x version. This version is no longer maintained. Please use `@stryker-mutator/core`. See https://stryker-mutator.io/blog/2019-02-13/announcing-stryker-1-0 for the full migration guide.
 npm warn deprecated stryker@1.0.1: Stryker v1 is released, b...

GitHub Actions: Diff Coverage / 0_Diff Coverage.txt: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run npx vitest run --coverage --coverage.reporter=json-summary --coverage.reporter=text
 �[36;1mnpx vitest run --coverage --coverage.reporter=json-summary --coverage.reporter=text�[0m
 shell: /usr/bin/bash -e {0}
 ##[endgroup]
 �[33m(!) Your Vite config uses features that are unsupported by `configLoader: 'native'`, which is planned to become the default in a future major version of Vite:
   - ESM syntax in a file loaded as CommonJS (vitest.config.ts:4:1). Use a `.mjs` extension or set `"type": "module"` in the closest package.json
 Set `VITE_CONFIG_NATIVE_IGNORE_WARNING=true` to suppress this warning.�[39m
 �[1m�[30m�[41m MISSING DEPENDENCY �[49m�[39m�[22m �[31mCannot find dependency '`@vitest/coverage-v8`'
 �[39m
 ##[error]Process completed with exit code 1.

GitHub Actions: Dependency Vulnerability Scan / 0_Dependency Review.txt: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48
 with:
   fail-on-severity: high
   comment-summary-in-pr: always
   deny-licenses: GPL-2.0, GPL-3.0, AGPL-3.0
   repo-***REDACTED_SECRET_ASSIGNMENT***
 ##[endgroup]
 ##[error]Dependency review is not supported on this repository. Please ensure that Dependency graph is enabled, see https://github.com/SamuelIVX/paycore/settings/security_analysis

GitHub Actions: Build / 0_Build.txt: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run npm run build
 �[36;1mnpm run build�[0m
 shell: /usr/bin/bash -e {0}
 env:
   NEXT_PUBLIC_SUPABASE_URL: https://example.supabase.co
   NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY: ci-placeholder-key
 ##[endgroup]
 > paycore@0.1.0 build
 > next build
 ▲ Next.js 16.3.4 (Turbopack)
 ✓ Running next.config.ts took 19ms
 ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
 Attention: Next.js now collects completely anonymous telemetry regarding usage.
 This information is used to shape Next.js' roadmap and prioritize features.
 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
 https://nextjs.org/telemetry
   Creating an optimized production build ...
 ✓ Compiled successfully in 8.2s
   Running TypeScript ...
 ##[error]app/employee/paystubs/__tests__/PayStubs.test.tsx(111,62): error TS2339: Property 'toBeInTheDocument' does not exist on type 'Assertion<void, HTMLElement>'.

GitHub Actions: Mutation Testing / Mutation Testing: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run if [ "pull_request" = "pull_request" ]; then
 �[36;1mif [ "pull_request" = "pull_request" ]; then�[0m
 �[36;1m  npx stryker run --since="origin/main"�[0m
 �[36;1melse�[0m
 �[36;1m  npx stryker run�[0m
 �[36;1mfi�[0m
 shell: /usr/bin/bash -e {0}
 ##[endgroup]
 npm warn exec The following package was not found and will be installed: stryker@1.0.1
 npm warn deprecated date-format@0.0.0: 0.x is no longer supported. Please upgrade to 4.x or higher.
 npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
 npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
 npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
 npm warn deprecated glob@5.0.15: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
 npm warn deprecated streamroller@0.4.1: 0.x is no longer supported. Please upgrade to 3.x or higher.
 npm warn deprecated istanbul@0.4.5: This module is no longer maintained, try this instead:
 npm warn deprecated   npm i nyc
 npm warn deprecated Visit https://istanbul.js.org/integrations for other alternatives.
 npm warn deprecated stryker-api@0.9.0: Stryker v1 is released, but you're still using a 0.x version. This version is no longer maintained. Please use `@stryker-mutator/core`. See https://stryker-mutator.io/blog/2019-02-13/announcing-stryker-1-0 for the full migration guide.
 npm warn deprecated stryker@1.0.1: Stryker v1 is released, b...

GitHub Actions: Diff Coverage / Diff Coverage: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run npx vitest run --coverage --coverage.reporter=json-summary --coverage.reporter=text
 �[36;1mnpx vitest run --coverage --coverage.reporter=json-summary --coverage.reporter=text�[0m
 shell: /usr/bin/bash -e {0}
 ##[endgroup]
 �[33m(!) Your Vite config uses features that are unsupported by `configLoader: 'native'`, which is planned to become the default in a future major version of Vite:
   - ESM syntax in a file loaded as CommonJS (vitest.config.ts:4:1). Use a `.mjs` extension or set `"type": "module"` in the closest package.json
 Set `VITE_CONFIG_NATIVE_IGNORE_WARNING=true` to suppress this warning.�[39m
 �[1m�[30m�[41m MISSING DEPENDENCY �[49m�[39m�[22m �[31mCannot find dependency '`@vitest/coverage-v8`'
 �[39m
 ##[error]Process completed with exit code 1.

GitHub Actions: Dependency Vulnerability Scan / Dependency Review: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48
 with:
   fail-on-severity: high
   comment-summary-in-pr: always
   deny-licenses: GPL-2.0, GPL-3.0, AGPL-3.0
   repo-***REDACTED_SECRET_ASSIGNMENT***
 ##[endgroup]
 ##[error]Dependency review is not supported on this repository. Please ensure that Dependency graph is enabled, see https://github.com/SamuelIVX/paycore/settings/security_analysis

GitHub Actions: Build / Build: chore(deps): update dependency vitest to v5

Conclusion: failure

View job details

##[group]Run npm run build
 �[36;1mnpm run build�[0m
 shell: /usr/bin/bash -e {0}
 env:
   NEXT_PUBLIC_SUPABASE_URL: https://example.supabase.co
   NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY: ci-placeholder-key
 ##[endgroup]
 > paycore@0.1.0 build
 > next build
 ▲ Next.js 16.3.4 (Turbopack)
 ✓ Running next.config.ts took 19ms
 ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
 Attention: Next.js now collects completely anonymous telemetry regarding usage.
 This information is used to shape Next.js' roadmap and prioritize features.
 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
 https://nextjs.org/telemetry
   Creating an optimized production build ...
 ✓ Compiled successfully in 8.2s
   Running TypeScript ...
 ##[error]app/employee/paystubs/__tests__/PayStubs.test.tsx(111,62): error TS2339: Property 'toBeInTheDocument' does not exist on type 'Assertion<void, HTMLElement>'.
🔇 Additional comments (1)
package.json (1)

52-52: 🎯 Functional Correctness

No compatibility issue is established for the Vitest upgrade.

CI uses Node.js 24, the lockfile resolves Vite 8.2.2, and the repository uses supported Vitest imports and configuration.

📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the development testing tool to version 5.0.0.

Walkthrough

The pull request updates the vitest development dependency from ^4.0.18 to ^5.0.0.

Changes

Vitest upgrade

Layer / File(s) Summary
Update Vitest development dependency
package.json		 The vitest development dependency range changes from ^4.0.18 to ^5.0.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 220c2

This updates the development test runner to Vitest 5 with synchronized dependency metadata. No current compatibility failure or production-impacting issue is evidenced, so the change is ready to merge.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly identifies the main change: updating the Vitest dependency to version 5. It is concise and specific.
Description check ✅ Passed The description directly explains the Vitest dependency update and includes relevant release notes and configuration details.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/major-vitest-monorepo

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies size/M

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@SamuelIVX