Skip to content

Update vitest npm packages#8264

Open
hash-worker[bot] wants to merge 1 commit intomainfrom
deps/js/vitest-npm-packages
Open

Update vitest npm packages#8264
hash-worker[bot] wants to merge 1 commit intomainfrom
deps/js/vitest-npm-packages

Conversation

@hash-worker
Copy link
Contributor

@hash-worker hash-worker bot commented Jan 17, 2026

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 4.0.16 -> 4.0.18 age confidence
vitest (source) 4.0.17 -> 4.0.18 age confidence
vitest-browser-react 2.0.2 -> 2.0.5 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

vitest-dev/vitest (vitest)

v4.0.18

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.17

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub
vitest-community/vitest-browser-react (vitest-browser-react)

v2.0.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🐞 Bug Fixes
  • Use a simple counter for act  -  by @​ocavue in #​43 (8b122)
  • Attach a stable testid to default baseElement and container  -  by @​nizans in #​44 (e8acb)
    • Warning: If you are using snapshots with container, update to Vitest 4.0.18 to avoid rendering injected data-testid attribute.
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "before 4am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@hash-worker hash-worker bot enabled auto-merge January 17, 2026 18:13
@cursor
Copy link

cursor bot commented Jan 17, 2026

PR Summary

Low Risk
Lockfile-only test tooling upgrade; risk is limited to potential CI/test behavior changes from the vitest patch update.

Overview
Updates the @hashintel/petrinaut dev dependency on vitest from 4.0.16 to 4.0.18.

Refreshes yarn.lock accordingly, upgrading the vitest package set (including @vitest/* subpackages) and bumping vitest-browser-react from 2.0.2 to 2.0.5.

Written by Cursor Bugbot for commit b39527b. This will update automatically on new commits. Configure here.

@github-actions github-actions bot added area/deps Relates to third-party dependencies (area) area/libs Relates to first-party libraries/crates/packages (area) type/eng > frontend Owned by the @frontend team labels Jan 17, 2026
@augmentcode
Copy link

augmentcode bot commented Jan 17, 2026

🤖 Augment PR Summary

Summary: Updates the Vitest test runner dependency for @hashintel/petrinaut from 4.0.16 to 4.0.17 (Renovate-managed bump).

Changes:

  • Bumped vitest version in libs/@hashintel/petrinaut/package.json.
  • Updated yarn.lock to align lockfile resolutions with the new version.

Technical Notes: Vitest 4.0.17 includes various bug fixes and adds experimental OpenTelemetry support; CI/test runs should confirm there are no behavioral regressions.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

@graphite-app graphite-app bot requested a review from a team January 17, 2026 18:21
TimDiekmann
TimDiekmann previously approved these changes Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 23, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 23, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 24, 2026
@hash-worker hash-worker bot added this pull request to the merge queue Jan 24, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 24, 2026
@TimDiekmann TimDiekmann dismissed their stale review January 24, 2026 10:45

Still failing

@hash-worker hash-worker bot enabled auto-merge January 24, 2026 10:46
@hash-worker hash-worker bot force-pushed the deps/js/vitest-npm-packages branch from 6b1c636 to 642d89a Compare January 24, 2026 11:13
@vercel
Copy link

vercel bot commented Jan 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hash Ready Ready Preview, Comment Feb 16, 2026 6:03pm
hashdotdesign Ready Ready Preview, Comment Feb 16, 2026 6:03pm
hashdotdesign-tokens Ready Ready Preview, Comment Feb 16, 2026 6:03pm
petrinaut Ready Ready Preview Feb 16, 2026 6:03pm

@hash-worker hash-worker bot force-pushed the deps/js/vitest-npm-packages branch from 642d89a to 58d6259 Compare January 25, 2026 17:44
@hash-worker hash-worker bot changed the title Update npm package vitest to v4.0.17 Update vitest npm packages Jan 25, 2026
@hash-worker hash-worker bot force-pushed the deps/js/vitest-npm-packages branch from 58d6259 to d016cbd Compare January 25, 2026 18:16
@hash-worker hash-worker bot force-pushed the deps/js/vitest-npm-packages branch from d016cbd to d84f112 Compare January 31, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/deps Relates to third-party dependencies (area) area/libs Relates to first-party libraries/crates/packages (area) type/eng > frontend Owned by the @frontend team

Development

Successfully merging this pull request may close these issues.

3 participants