Skip to content

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

Merged
pokutuna merged 2 commits into
masterfrom
renovate/major-5-major
Oct 2, 2026
Merged

chore(deps): update dependency vitest to v5#210
pokutuna merged 2 commits into
masterfrom
renovate/major-5-major

Conversation

@renovate

@renovate renovate Bot commented Sep 6, 2026 •
edited
Loading

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.10 → ^5.0.0 age confidence

Release Notes

vitest-dev/vitest (vitest)

v5.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

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: (in timezone Asia/Tokyo)

  • Branch creation
    • "before 10:00 on Monday"
  • 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 added the renovate label Sep 6, 2026
@renovate
renovate Bot force-pushed the renovate/major-5-major branch from 0da1575 to 6cbbf06 Compare September 10, 2026 20:57
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 chore(deps): update dependency vitest to v5 - autoclosed Sep 11, 2026
@renovate renovate Bot closed this Sep 11, 2026
@renovate
renovate Bot deleted the renovate/major-5-major branch September 11, 2026 03:16
@renovate renovate Bot changed the title chore(deps): update dependency vitest to v5 - autoclosed chore(deps): update dependency vitest to v5 Sep 13, 2026
@renovate renovate Bot reopened this Sep 13, 2026
@renovate
renovate Bot force-pushed the renovate/major-5-major branch 2 times, most recently from 6cbbf06 to 060cdb1 Compare September 13, 2026 17:56
@renovate
renovate Bot force-pushed the renovate/major-5-major branch 2 times, most recently from 1e92dc2 to 63bafd0 Compare October 1, 2026 03:34
@renovate
renovate Bot force-pushed the renovate/major-5-major branch from 63bafd0 to 7857d84 Compare October 2, 2026 09:09
@renovate

renovate Bot commented Oct 2, 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
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 33, reused 0, downloaded 0, added 0
Progress: resolved 36, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "why-is-node-running@3.2.2" (possible package takeover)

This error happened while installing the dependencies of vitest@5.0.2

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

@pokutuna
fix: use jest-dom vitest entry for Vitest 5 matcher types
54a29f4 
Vitest 5 no longer extends the global jest.Matchers namespace, so the
root @testing-library/jest-dom import stopped typing toBeInTheDocument
and friends. Import @testing-library/jest-dom/vitest instead.

Lock vitest to 5.0.1: 5.0.2 pulls why-is-node-running@3.2.2 which fails
pnpm trustPolicy (ERR_PNPM_TRUST_DOWNGRADE), and 5.0.3 (which pins 3.2.1)
is still within minimumReleaseAge.
@pokutuna

pokutuna commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Manual follow-up before merge:

  • Vitest 5 no longer extends the global jest.Matchers namespace, so tests now import @testing-library/jest-dom/vitest (fixes TS2339 on toBeInTheDocument).
  • Lockfile regenerated on top of master and locked to vitest 5.0.1: 5.0.2 depends on why-is-node-running@3.2.2 (published without provenance) and trips trustPolicy: no-downgrade (ERR_PNPM_TRUST_DOWNGRADE). 5.0.3 pins 3.2.1 upstream but is still inside minimumReleaseAge.
  • Verified locally: vitest 5.0.1 (281 passed), oxlint/oxfmt/tsc, build, Playwright e2e (17 passed), update-gallery.

@pokutuna
pokutuna merged commit 7c7cd08 into master Oct 2, 2026
1 check passed
@pokutuna pokutuna mentioned this pull request Oct 2, 2026
Merged
1 task
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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@pokutuna