feat: update security endpoint response and fix for last 24 hours #15
BccorbAnnotations
5 errors and 1 warning
|
test
Process completed with exit code 1.
|
|
tests/unit/lib/token.spec.ts > token utils > signs ephemeral token:
tests/unit/lib/token.spec.ts#L102
TypeError: getSigningKey.mockResolvedValue is not a function
❯ tests/unit/lib/token.spec.ts:102:28
|
|
tests/unit/lib/token.spec.ts > token utils > signs refresh token:
tests/unit/lib/token.spec.ts#L83
TypeError: getSigningKey.mockResolvedValue is not a function
❯ tests/unit/lib/token.spec.ts:83:28
|
|
tests/unit/lib/token.spec.ts > token utils > signs access token:
tests/unit/lib/token.spec.ts#L63
TypeError: getSigningKey.mockResolvedValue is not a function
❯ tests/unit/lib/token.spec.ts:63:28
|
|
tests/integration/internal/internal.spec.ts > GET /internal/security/anomalies > returns anomalies:
tests/integration/internal/internal.spec.ts#L101
TypeError: Cannot read properties of undefined (reading 'length')
❯ tests/integration/internal/internal.spec.ts:101:35
|
|
test
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. 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/
|