chore: trigger redeploy 2 #32
ci-cd-pipeline.yml
on: push
Server — Build & Test
1m 18s
Client — Build & Lint
48s
Security Audit
29s
Deploy
4s
Annotations
3 errors and 4 warnings
|
src/__tests__/epic5/us5.3-bulk-import.test.ts:
server/src/__tests__/setup/testSetup.ts#L86
Error: Failed to authenticate test user: Request rate limit reached
❯ getAdminToken src/__tests__/setup/testSetup.ts:86:15
❯ src/__tests__/epic5/us5.3-bulk-import.test.ts:24:5
|
|
src/__tests__/epic4/approvalWorkflow.test.ts:
server/src/services/bookingService.ts#L10
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock
❯ src/services/bookingService.ts:10:1
Caused by: Caused by: ReferenceError: Cannot access 'mockSupabase' before initialization
❯ src/__tests__/epic4/approvalWorkflow.test.ts:24:15
|
|
src/__tests__/epic3/us3.7-waitlist.test.ts > US 3.7: Waitlist Notification > Waitlist Notification on Booking Cancellation > should notify the first user in the waitlist when a booking is cancelled:
server/src/__tests__/epic3/us3.7-waitlist.test.ts#L255
AssertionError: expected 403 to be 201 // Object.is equality
- Expected
+ Received
- 201
+ 403
❯ src/__tests__/epic3/us3.7-waitlist.test.ts:255:39
|
|
Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Client — Build & Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Server — Build & Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|