Skip to content

chore(deps): use pnpm workspace anchor for vitest versions - #3215

Merged
setchy merged 8 commits into
mainfrom
renovate/vite-plus-vitest
Aug 24, 2026
Merged

chore(deps): use pnpm workspace anchor for vitest versions#3215
setchy merged 8 commits into
mainfrom
renovate/vite-plus-vitest

Conversation

@renovate

@renovaterenovateBot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
@vitest/browser (source)4.1.104.1.11ageconfidence
@vitest/browser-playwright (source)4.1.104.1.11ageconfidence
@vitest/coverage-v8 (source)4.1.104.1.11ageconfidence
vitest (source)4.1.104.1.11ageconfidence

Release Notes

vitest-dev/vitest (@​vitest/browser)

v4.1.11

Compare Source

🐞 Bug Fixes
View changes on GitHub

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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.

@renovaterenovateBot added the dependency Dependency updates label Aug 22, 2026
@renovaterenovateBot added the dependency Dependency updates label Aug 22, 2026
@renovate
renovateBotforce-pushed the renovate/vite-plus-vitest branch 2 times, most recently from 955fb3e to d15ebaaCompareAugust 22, 2026 12:02
@renovate
renovateBotforce-pushed the renovate/vite-plus-vitest branch from d15ebaa to 8799c3fCompareAugust 22, 2026 13:11
@setchy

Copy link
Copy Markdown
Member

Failure is due to vite-plus still requiring 4.1.10, while the rest of the toolchain is up to 4.1.11

@renovate
renovateBotforce-pushed the renovate/vite-plus-vitest branch 2 times, most recently from 1226ede to 146e800CompareAugust 24, 2026 11:12
@renovate
renovateBotforce-pushed the renovate/vite-plus-vitest branch from 146e800 to 23298b6CompareAugust 24, 2026 11:19
vite-plus 0.2.9 hard-pins vitest 4.1.10 internally and vp test runs
through that copy, so renovate's grouped bump to vitest 4.1.11 loaded
two incompatible copies into the test workers and broke every
rejects/.resolves.toThrow() assertion (152 failures).
- drop @vitest/browser: bundled by vite-plus, nothing imports it
- pin vitest/@vitest/browser-playwright/@vitest/coverage-v8 in
pnpm-workspace.yaml overrides so a split can never resolve at runtime
- replace the two renovate holds with a single cap on the vitest family,
kept only to avoid no-op PRs while vite-plus still bundles 4.1.10
…-app/gitify into renovate/vite-plus-vitest
# Conflicts:
#	package.json
#	pnpm-lock.yaml
Move the vitest family versions (vitest, @vitest/browser-playwright,
@vitest/coverage-v8) into pnpm-workspace.yaml's catalog and reference
them via catalog: in package.json, with the overrides following the
catalog (electron-style). The catalog is now the single source of truth.
Drop the static allowedVersions hold in renovate.json. The global
override referencing the catalog forces every copy - including vite-plus's
bundled vitest - onto one version, so a renovate bump of the catalog while
vite-plus lags can no longer split the copies that broke every
rejects/.resolves.toThrow() assertion. Verified: forcing the catalog to
4.1.11 (vite-plus still 0.2.9) keeps all 1373 tests green.
@renovate

renovateBot commented Aug 24, 2026

Copy link
Copy Markdown
ContributorAuthor

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.

@afonsojramos

Copy link
Copy Markdown
Member

@setchy does that really solve the issue here?

@setchy

Copy link
Copy Markdown
Member

@setchy does that really solve the issue here?

WIP - wifi on my flight was patchy. Marking as draft

@setchysetchy self-assigned this Aug 24, 2026
@setchy
setchy marked this pull request as draft August 24, 2026 17:27
…th YAML anchor
electron was hardcoded in package.json (43.2.0) AND in pnpm-workspace.yaml's
catalog, duplicating the version in two places. Point it at catalog: so the
catalog is the single source of truth, matching the vitest family.
The vitest family (vitest, @vitest/browser-playwright, @vitest/coverage-v8)
shares one bundled version; use a YAML anchor so the version is defined once
instead of repeated three times.
@setchysetchy changed the title chore(deps): update vite-plus / vitest to v4.1.11chore(deps): use pnpm workspace anchor for vitest versionsAug 24, 2026
Signed-off-by: Adam Setch <adam.setch@outlook.com>
@setchy
setchy marked this pull request as ready for review August 24, 2026 19:32
@setchy

Copy link
Copy Markdown
Member

not a complete fix, but a step or two in the right direction

@setchy
setchy merged commit 614c2e3 into mainAug 24, 2026
20 checks passed
@setchy
setchy deleted the renovate/vite-plus-vitest branch August 24, 2026 19:35
@github-actionsgithub-actionsBot added this to the Release 7.x.x milestone Aug 24, 2026
@sonarqubecloud

Copy link
Copy Markdown

@setchysetchy mentioned this pull request Aug 31, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencyDependency updates

Development

Successfully merging this pull request may close these issues.

2 participants

@setchy@afonsojramos