Add functionality to restrict or unrestrict users #12807
Annotations
7 errors and 2 warnings
|
E2E Tests (Node 22.x, Freestyle mock)
Process completed with exit code 1.
|
|
src/auto-migrations/migration-tests.test.ts > database migration tests > 20260420000000_add_project_onboarding_state > default-and-updates:
apps/backend/prisma/migrations/20260420000000_add_project_onboarding_state/tests/default-and-updates.ts#L42
Error: Snapshot `database migration tests > 20260420000000_add_project_onboarding_state > default-and-updates 1` mismatched
- Expected
+ Received
- {
- "selected_apps": [
- "authentication",
- "emails",
- ],
- "selected_config_choice": "create-new",
- "selected_email_theme_id": null,
- "selected_payments_country": "US",
- "selected_sign_in_methods": [
- "credential",
- "magicLink",
- ],
- }
+ "{"selected_config_choice":"create-new","selected_apps":["authentication","emails"],"selected_sign_in_methods":["credential","magicLink"],"selected_email_theme_id":null,"selected_payments_country":"US"}"
❯ Module.postMigration prisma/migrations/20260420000000_add_project_onboarding_state/tests/default-and-updates.ts:42:54
❯ src/auto-migrations/migration-tests.test.ts:148:13
|
|
tests/backend/endpoints/api/v1/auth/cli/route.test.ts > should create a new CLI auth attempt with custom expiration time:
apps/e2e/tests/backend/endpoints/api/v1/auth/cli/route.test.ts#L35
AssertionError: expected 400 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 400
❯ tests/backend/endpoints/api/v1/auth/cli/route.test.ts:35:27
|
|
tests/backend/endpoints/api/v1/auth/cli/route.test.ts > should create a new CLI auth attempt:
apps/e2e/tests/backend/endpoints/api/v1/auth/cli/route.test.ts#L20
AssertionError: expected 119967 to be greater than 7190000
❯ tests/backend/endpoints/api/v1/auth/cli/route.test.ts:20:47
|
|
tests/backend/endpoints/api/v1/internal-metrics.test.ts > should return metrics data with users:
apps/e2e/tests/backend/endpoints/api/v1/internal-metrics.test.ts#L179
Error: Snapshot `should return metrics data with users > metrics_result_with_users 1` mismatched
- Expected
+ Received
@@ -5,19 +5,19 @@
"AQ": [
{
"display_name": null,
"id": "<stripped UUID>",
"last_active_at_millis": <stripped field 'last_active_at_millis'>,
- "primary_email": "mailbox-1--<stripped UUID>@stack-generated.example.com",
+ "primary_email": "mailbox-2--<stripped UUID>@stack-generated.example.com",
"profile_image_url": null,
"signed_up_at_millis": <stripped field 'signed_up_at_millis'>,
},
{
"display_name": null,
"id": "<stripped UUID>",
"last_active_at_millis": <stripped field 'last_active_at_millis'>,
- "primary_email": "mailbox-2--<stripped UUID>@stack-generated.example.com",
+ "primary_email": "mailbox-1--<stripped UUID>@stack-generated.example.com",
"profile_image_url": null,
"signed_up_at_millis": <stripped field 'signed_up_at_millis'>,
},
],
"CH": [
❯ it.timeout tests/backend/endpoints/api/v1/internal-metrics.test.ts:179:20
|
|
E2E Tests (Node 22.x, Freestyle prod)
The strategy configuration was canceled because "build._22_x_mock" failed
|
|
E2E Tests (Node 22.x, Freestyle prod)
The operation was canceled.
|
|
E2E Tests (Node 22.x, Freestyle mock)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, 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/
|
|
E2E Tests (Node 22.x, Freestyle prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, 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/
|