Skip to content

feat(access-control): add ALLOWED_INTEGRATIONS env var for self-hosted block restrictions #10207

feat(access-control): add ALLOWED_INTEGRATIONS env var for self-hosted block restrictions

feat(access-control): add ALLOWED_INTEGRATIONS env var for self-hosted block restrictions #10207

Triggered via pull request February 18, 2026 02:29
Status Failure
Total duration 2m 18s
Artifacts

ci.yml

on: pull_request
Detect Version
0s
Detect Version
Test and Build  /  Test and Build
1m 57s
Test and Build / Test and Build
Check Docs Changes
0s
Check Docs Changes
Matrix: Build AMD64
Matrix: Build ARM64 (GHCR Only)
Process Docs  /  Process Documentation Embeddings
Process Docs / Process Documentation Embeddings
Matrix: Create GHCR Manifests
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Test and Build / Test and Build
Process completed with exit code 1.
Test and Build / Test and Build
sim#test: command (/home/runner/_work/sim/sim/apps/sim) /home/runner/.bun/bin/bun run test exited (1)
ee/access-control/utils/permission-check.test.ts: apps/sim/ee/access-control/utils/permission-check.test.ts#L55
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 ❯ ee/access-control/utils/permission-check.test.ts:55:1 Caused by: Caused by: ReferenceError: Cannot access 'mockGetAllowedIntegrationsFromEnv' before initialization ❯ ee/access-control/utils/permission-check.test.ts:40:34 ❯ ee/access-control/utils/permission-check.test.ts:55:1
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
- Step: unknown (failed)
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps