Skip to content

chore(deps): update vitest #17949

chore(deps): update vitest

chore(deps): update vitest #17949

Triggered via pull request May 11, 2026 05:52
Status Failure
Total duration 2m 49s
Artifacts

ci.yml

on: pull_request
Matrix: Build & Test
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 1 warning
Lint
Process completed with exit code 1.
Lint: test/global.setup.ts#L27
Property 'file' does not exist on type 'object'.
[integration] server/documents/integration.test.ts: server/tsyringe.ts#L148
Error: No constructor registered for Symbol(PrismaClient) ❯ resolve server/tsyringe.ts:148:11 ❯ Module.disconnect server/database/disconnect.ts:4:9 ❯ server/documents/integration.test.ts:12:16
[integration] server/documents/integration.test.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[integration] server/database/integration.test.ts: server/tsyringe.ts#L148
Error: No constructor registered for Symbol(PrismaClient) ❯ resolve server/tsyringe.ts:148:11 ❯ Module.disconnect server/database/disconnect.ts:4:9 ❯ server/database/integration.test.ts:10:16
[integration] server/database/integration.test.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[unit] server/utils/validation.spec.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[unit] server/utils/crypto.spec.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[unit] server/user/resolvers.spec.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[unit] server/journals/journal.service.spec.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[unit] server/documents/user.document.service.spec.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
[unit] server/documents/resolvers.spec.ts: test/global.setup.ts#L24
FixtureParseError: The 1st argument inside a fixture must use object destructuring pattern, e.g. ({ task } => {}). Instead, received "context". If you used internal "suite" task as the 1st argument previously, access it in the 2nd argument instead. ❯ test/global.setup.ts:24:1
Build & Test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: chromaui/action@eea1606238fd97a70b5af723d103953d1f40967b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/