Skip to content

chore(deps): update vitest monorepo to v5 - #148

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

chore(deps): update vitest monorepo to v5#148
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Aug 22, 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/coverage-v8 (source) ^3.2.7 → ^5.0.0 age confidence
vitest (source) ^3.2.7 → ^5.0.0 age confidence

Release Notes

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

v5.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/Denver)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • "after 5pm and before 9pm every weekday"

🚦 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 a team as a code owner August 22, 2026 01:35
@renovate renovate Bot added dependencies Pull requests that update a dependency file major-update needs-review renovate labels Aug 22, 2026
@renovate

renovate Bot commented Aug 22, 2026 •
edited
Loading

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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/build@20.3.34
npm error Found: vitest@5.0.0
npm error node_modules/vitest
npm error   dev vitest@"^5.0.0" from the root project
npm error   peerOptional vitest@">= 0.32" from @testing-library/jest-dom@7.0.1
npm error   node_modules/@testing-library/jest-dom
npm error     dev @testing-library/jest-dom@"^7.0.1" from @contentful/experiences-angular@0.1.1
npm error     packages/adapter-angular
npm error       @contentful/experiences-angular@0.1.1
npm error       node_modules/@contentful/experiences-angular
npm error         workspace packages/adapter-angular from the root project
npm error         1 more (@contentful/experiences-example-angular)
npm error     dev @testing-library/jest-dom@"^7.0.1" from @contentful/experiences-svelte@0.6.1
npm error     packages/adapter-svelte
npm error       @contentful/experiences-svelte@0.6.1
npm error       node_modules/@contentful/experiences-svelte
npm error         workspace packages/adapter-svelte from the root project
npm error         2 more (@contentful/experiences-example-sveltekit, @contentful/experiences-testapp-sveltekit)
npm error   2 more (@testing-library/svelte, @vitest/coverage-v8)
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^3.1.1" from @angular/build@20.3.34
npm error examples/angular/node_modules/@angular/build
npm error   dev @angular/build@"^20.3.34" from @contentful/experiences-example-angular@0.0.0
npm error   examples/angular
npm error     @contentful/experiences-example-angular@0.0.0
npm error     node_modules/@contentful/experiences-example-angular
npm error       workspace examples/angular from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-05T12_35_02_804Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-05T12_35_02_804Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 4ae63d4 to 9d5ab72 Compare August 27, 2026 00:19
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from f88d440 to 3492127 Compare September 3, 2026 07:51
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 3492127 to ef08d33 Compare September 5, 2026 12:35
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4 chore(deps): update vitest monorepo to v5 Sep 5, 2026
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 Pull requests that update a dependency file major-update needs-review renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants