Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 4.1.105.0.1 age confidence

Release Notes

vitest-dev/vitest (vitest)

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 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.

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 0a262a2 to c5ac2c4 Compare September 15, 2026 18:50
@renovate

renovate Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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
✓ Lockfile passes supply-chain policies (verified 5s ago)
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 177, reused 0, downloaded 0, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 3 versions do not meet the minimumReleaseAge constraint:
  @vitest/mocker@5.0.1 was published at 2026-09-15T08:50:30.600Z, within the minimumReleaseAge cutoff (2026-09-13T18:50:03.570Z)
  @vitest/spy@5.0.1 was published at 2026-09-15T08:50:53.820Z, within the minimumReleaseAge cutoff (2026-09-13T18:50:03.570Z)
  vitest@5.0.1 was published at 2026-09-15T08:49:35.830Z, within the minimumReleaseAge cutoff (2026-09-13T18:50:03.570Z)

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.

0 participants