Skip to content

feat: support args.receiverAddress override + allow zero ERC-20 approvals #73

feat: support args.receiverAddress override + allow zero ERC-20 approvals

feat: support args.receiverAddress override + allow zero ERC-20 approvals #73

Triggered via pull request March 31, 2026 03:29
Status Failure
Total duration 27s
Artifacts

ci.yml

on: pull_request
Security Audit
16s
Security Audit
Matrix: Test & Build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 23 warnings
Security Audit
Process completed with exit code 1.
Test & Build (22.x)
Process completed with exit code 1.
Test & Build (20.17.0)
The strategy configuration was canceled because "test._22_x" failed
Test & Build (20.17.0)
The operation was canceled.
Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Test & Build (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Test & Build (22.x): src/validators/evm/erc4626/erc4626.validator.ts#L214
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
Test & Build (22.x): src/validators/evm/erc4626/erc4626.validator.ts#L126
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
Test & Build (22.x): src/validators/evm/erc4626/erc4626.validator.ts#L121
Unexpected nullable number value in conditional. Please handle the nullish/zero/NaN cases explicitly
Test & Build (22.x): src/validators/evm/erc4626/erc4626.exhaustive-coverage.test.ts#L103
Unexpected nullable boolean value in conditional. Please handle the nullish case explicitly
Test & Build (22.x): src/shield.test.ts#L368
Unexpected any. Specify a different type
Test & Build (22.x): src/shield.test.ts#L344
Unexpected any. Specify a different type
Test & Build (22.x): src/shield.test.ts#L320
Unexpected any. Specify a different type
Test & Build (22.x): src/shield.test.ts#L291
Unexpected any. Specify a different type
Test & Build (22.x): src/shield.test.ts#L215
Unexpected any. Specify a different type
Test & Build (22.x): src/shield.test.ts#L71
Unexpected any. Specify a different type
Test & Build (20.17.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Test & Build (20.17.0): src/validators/evm/erc4626/erc4626.validator.ts#L214
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
Test & Build (20.17.0): src/validators/evm/erc4626/erc4626.validator.ts#L126
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
Test & Build (20.17.0): src/validators/evm/erc4626/erc4626.validator.ts#L121
Unexpected nullable number value in conditional. Please handle the nullish/zero/NaN cases explicitly
Test & Build (20.17.0): src/validators/evm/erc4626/erc4626.exhaustive-coverage.test.ts#L103
Unexpected nullable boolean value in conditional. Please handle the nullish case explicitly
Test & Build (20.17.0): src/shield.test.ts#L368
Unexpected any. Specify a different type
Test & Build (20.17.0): src/shield.test.ts#L344
Unexpected any. Specify a different type
Test & Build (20.17.0): src/shield.test.ts#L320
Unexpected any. Specify a different type
Test & Build (20.17.0): src/shield.test.ts#L291
Unexpected any. Specify a different type
Test & Build (20.17.0): src/shield.test.ts#L215
Unexpected any. Specify a different type
Test & Build (20.17.0): src/shield.test.ts#L71
Unexpected any. Specify a different type