Skip to content

chore(repo): Update testing to v4 (major)#8443

Open
renovate[bot] wants to merge 13 commits intomainfrom
renovate/major-testing
Open

chore(repo): Update testing to v4 (major)#8443
renovate[bot] wants to merge 13 commits intomainfrom
renovate/major-testing

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 2, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 3.2.4 → 4.1.5 age adoption passing confidence
vitest (source) 3.2.4 → 4.1.5 age adoption passing confidence

Warning

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

Release Notes

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

v4.1.5

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.3

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.2

Compare Source

This release bumps Vitest's flatted version and removes version pinning to resolve flatted's CVE related issues (#​9975).

   🐞 Bug Fixes
    View changes on GitHub

v4.1.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.0

Compare Source

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features
   🐞 Bug Fixes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone GMT)

  • Branch creation
    • "before 7am on the first day of the week"
  • 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.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label May 2, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 2, 2026 •
edited
Loading

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

Project Deployment Actions Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment May 6, 2026 3:00am

Request Review

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 2, 2026 •
edited
Loading

⚠️ 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

<--- Last few GCs --->

[939:0x16ab6000]   130969 ms: Mark-Compact (reduce) 1477.4 (1489.1) -> 1471.7 (1483.9) MB, pooled: 0 MB, 1112.71 / 0.46 ms  (+ 221.1 ms in 66 steps since start of marking, biggest step 19.9 ms, walltime since start of marking 1656 ms) (average mu = 0.388,
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x73f8c4 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/opt/containerbase/tools/node/24.15.0/bin/node]
 2: 0xc06f90  [/opt/containerbase/tools/node/24.15.0/bin/node]
 3: 0xc0707f  [/opt/containerbase/tools/node/24.15.0/bin/node]
 4: 0xeaa885  [/opt/containerbase/tools/node/24.15.0/bin/node]
 5: 0xeaa8b2  [/opt/containerbase/tools/node/24.15.0/bin/node]
 6: 0xeaabaa  [/opt/containerbase/tools/node/24.15.0/bin/node]
 7: 0xebb8aa  [/opt/containerbase/tools/node/24.15.0/bin/node]
 8: 0xebfc50  [/opt/containerbase/tools/node/24.15.0/bin/node]
 9: 0x1953f71  [/opt/containerbase/tools/node/24.15.0/bin/node]
/usr/local/bin/node: line 18:   939 Aborted                 /opt/containerbase/tools/node/24.15.0/bin/node "$@"

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 2, 2026 •
edited
Loading

🦋 Changeset detected

Latest commit: 5eaf5ea

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 3, 2026 •
edited
Loading

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8443

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8443

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8443

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8443

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8443

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8443

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8443

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8443

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8443

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8443

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8443

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8443

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8443

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8443

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8443

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8443

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8443

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8443

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8443

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8443

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8443

commit: 5eaf5ea

@renovate renovate Bot force-pushed the renovate/major-testing branch from 03b7c43 to e63302f Compare May 5, 2026 19:39
jacekradko added 4 commits May 5, 2026 14:48
@jacekradko
chore(repo): pnpm dedupe
90b43ba
@jacekradko
fix(backend): use relative imports instead of bare 'src/...' paths
7f2427f 
Vitest 4 no longer resolves bare 'src/...' specifiers, breaking test loading in @clerk/backend.
@jacekradko
fix(backend): sort imports
1d7ee8a
@jacekradko
test(fastify): remove obsolete snapshots
11d3d2c 
Vitest 4 fails when obsolete snapshots are present rather than warning.
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 5, 2026

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.

@github-actions github-actions Bot added the react label May 5, 2026
@jacekradko
test(backend): drop redundant miniflare runtime, keep node + edge-run…
e1d2510 
…time

@clerk/backend uses no Workers-only APIs (no cloudflare:* imports, no
KV/DO/R2 bindings, no ExecutionContext, no caches.default), so the
miniflare run was duplicating signal already covered by the node and
edge-runtime runs. vitest-environment-miniflare 2.14.4 is incompatible
with vitest 4 and is unmaintained, blocking the upgrade.
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

backend chrome-extension clerk-js dependencies Pull requests that update a dependency file fastify react testing

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jacekradko