Skip to content

feat(hexclave): PR 1 — wire compatibility layer (invisible) #4483

feat(hexclave): PR 1 — wire compatibility layer (invisible)

feat(hexclave): PR 1 — wire compatibility layer (invisible) #4483

Triggered via pull request May 23, 2026 22:02
Status Failure
Total duration 29m 49s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build (22.x)
Process completed with exit code 1.
src/lib/redirect-urls.test.tsx > validateRedirectUrl > exact domain matching > should implicitly validate hosted handler domains for the project: apps/backend/src/lib/redirect-urls.test.tsx#L75
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ src/lib/redirect-urls.test.tsx:75:117 ❯ withHostedHandlerEnv src/lib/redirect-urls.test.tsx:30:14 ❯ src/lib/redirect-urls.test.tsx:64:7
build (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@2428e7b970a846423095c79d43f759abf979a635, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/