Repository navigation
chore(deps): bump vitest from 4.1.9 to 5.0.3 in /workers/commons-gateway - #69
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.9 to 5.0.3. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.3/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.3 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
floss | c6a1f8b | Oct 01 2026, 11:07 PM |
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…tibility (#77) ## Root cause #69 (c6a1f8b, merged 2026-10-01) raised `vitest` to `^5.0.3` in `workers/commons-gateway`. `@cloudflare/vitest-pool-workers` (0.22.0, and 0.23.0, the latest) declares peer `vitest ^4.1.0`, so `npm ci` cannot resolve the tree. **Evidence:** Workers Builds `67c454cb…` (#43) and `053a4309…` (#73) both fail at *Installing project dependencies: npm clean-install* with `npm error Cannot read properties of null (reading 'edgesOut')`, which is how npm 10.9.2 reports this peer conflict. npm 11 on the same tree prints `ERESOLVE … peer vitest@"^4.1.0" from @cloudflare/vitest-pool-workers@0.22.0`. `npm ci` fails the same way on `main`, #43, and #73. **Why main looked green:** the "Deploy non-production branches" trigger excludes `main`, so main never runs this check. #41 passed only because its branch predates #69. ## Change - Restore `vitest ^4.1.9` and the commons-gateway lockfile from before #69. - Bump `@cloudflare/workers-types` from `^4` to `^5.20261025.1`. Once the vitest conflict is gone, npm 10.9.2 reports a second one: wrangler 4.124.0 declares an optional peer of `workers-types ^5.20260815.1`. - `.github/dependabot.yml`: ignore `vitest >=5` for `/workers/commons-gateway` until pool-workers accepts it. The rest of the config is unchanged. ## Verification (node 24 + npm 10.9.2, matching the Cloudflare build image) - `npm ci`: ok - `vitest run`: 12/12 - `tsc --noEmit`: ok - `wrangler deploy --dry-run`: ok ## After merge #43 and #73 (and any branch with #69) need updating from `main` to get Workers Builds green again. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Chores** * Updated maintenance settings for the gateway’s development tools. Future automated updates will remain within the configured version range. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Bumps vitest from 4.1.9 to 5.0.3.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
33cadeachore: release v5.0.3 (#11409)346d389fix(vm): don't reuse scripts across vite environments (#11395)f6c9a49fix(deps): pinwhy-is-node-runningto3.2.1to avoid users running into `...062c75dchore: fix standalone docs build, update exports maps (#11394)caf2887fix(vm): do not optimize deps from index.html (fix #11329) (#11360)50312ebfix(pool): preserve unique pool ids whengroupOrderis set (#11392)7c36748fix(browser): ignore page crash while cancelling (#11386)92ba7fcfix: scope cache key generators to projects (fix #11281) (#11301)38f9885fix(cache): revalidate imports of cached modules (#11381)b24585ffix: don't retry whentest.failsexpectedly failed (#11219)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.