Skip to content

chore(deps): bump the minor-and-patch group across 1 directory with 4… #665

chore(deps): bump the minor-and-patch group across 1 directory with 4…

chore(deps): bump the minor-and-patch group across 1 directory with 4… #665

Status Failure
Total duration 3m 4s
Artifacts

ci.yml

on: push
Lint and Build
37s
Lint and Build
TypeScript Check
36s
TypeScript Check
Integration Tests
2m 52s
Integration Tests
E2E Tests  /  E2E Tests
1m 33s
E2E Tests / E2E Tests
Benchmark Tests  /  Benchmark Tests
1m 51s
Benchmark Tests / Benchmark Tests
Release Docker Image  /  Build Full Image
Release Docker Image / Build Full Image
Release Docker Image  /  Build Slim Image
Release Docker Image / Build Slim Image
Soak Tests  /  Benchmark Tests
Soak Tests / Benchmark Tests
Deploy to Production
0s
Deploy to Production
Release Docker Image  /  Create Release
Release Docker Image / Create Release
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 6 warnings
TypeScript Check
Process completed with exit code 2.
TypeScript Check: src/components/config-form.tsx#L1009
Type 'Control<FormValues, any, FormValues>' is not assignable to type 'Control<any>'.
TypeScript Check: src/components/config-form.tsx#L953
Type 'Control<FormValues, any, FormValues>' is not assignable to type 'Control<any>'.
TypeScript Check: src/app/layout.tsx#L75
Type '({ error, resetErrorBoundary }: ErrorFallbackProps) => Element' is not assignable to type 'ComponentType<FallbackProps> | undefined'.
Lint and Build
Process completed with exit code 1.
E2E Tests / E2E Tests
Process completed with exit code 1.
Benchmark Tests / Benchmark Tests
Process completed with exit code 1.
tests/admin-api/update-config.spec.ts > Admin API - Update Config > Environment Variants Updates > should add environment variants: tests/admin-api/update-config.spec.ts#L655
AssertionError: expected 400 to be 200 // Object.is equality - Expected + Received - 200 + 400 ❯ tests/admin-api/update-config.spec.ts:655:31
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Large Number of Configs > should list many configs: tests/admin-api/list-configs.spec.ts#L412
AssertionError: expected [] to have a length of 20 but got +0 - Expected + Received - 20 + 0 ❯ tests/admin-api/list-configs.spec.ts:412:28
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > After Deletion > should not list deleted configs: tests/admin-api/list-configs.spec.ts#L381
AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ tests/admin-api/list-configs.spec.ts:381:28
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Response Format > should reflect updated version in list: tests/admin-api/list-configs.spec.ts#L340
TypeError: Cannot read properties of undefined (reading 'version') ❯ tests/admin-api/list-configs.spec.ts:340:21
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Response Format > should return truncated description as descriptionPreview: tests/admin-api/list-configs.spec.ts#L303
TypeError: Cannot read properties of undefined (reading 'description') ❯ tests/admin-api/list-configs.spec.ts:303:21
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Response Format > should return configs with all expected fields: tests/admin-api/list-configs.spec.ts#L262
AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ tests/admin-api/list-configs.spec.ts:262:28
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Multiple Configs > should list configs only from the specified project: tests/admin-api/list-configs.spec.ts#L223
AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ tests/admin-api/list-configs.spec.ts:223:29
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Multiple Configs > should list multiple configs: tests/admin-api/list-configs.spec.ts#L178
AssertionError: expected [] to have a length of 3 but got +0 - Expected + Received - 3 + 0 ❯ tests/admin-api/list-configs.spec.ts:178:28
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Authorization > should list configs with unrestricted project access: tests/admin-api/list-configs.spec.ts#L120
AssertionError: expected 0 to be greater than or equal to 1 ❯ tests/admin-api/list-configs.spec.ts:120:35
tests/admin-api/list-configs.spec.ts > Admin API - List Configs > Authorization > should list configs with config:read scope: tests/admin-api/list-configs.spec.ts#L51
AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ tests/admin-api/list-configs.spec.ts:51:28
TypeScript Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
Lint and Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
Lint and Build: src/components/workspace-switcher.tsx#L33
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
E2E Tests / E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
Benchmark Tests / Benchmark Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/