error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-transfer-with-authorization.md | 313 | New contracts benefit from being able to directly utilize EIP-3009 in order to create atomic transactions, but existing contracts may still rely on the conventional ERC-20 allowance pattern (`approve`/`transferFrom`). | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-link-first/

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-transfer-with-authorization.md | 315 | In order to add support for EIP-3009 to existing contracts ("parent contract") that use the ERC-20 allowance pattern, a forwarding contract ("forwarder") can be constructed that takes an authorization and does the following: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-transfer-with-authorization.md | 524 | A fully working implementation of EIP-3009 can be found in [this repository](https://github.com/CoinbaseStablecoin/eip-3009/blob/master/contracts/lib/EIP3009.sol). The repository also includes [an implementation of EIP-2612](https://github.com/CoinbaseStablecoin/eip-3009/blob/master/contracts/lib/EI32612.sol) that uses the EIP-712 library code presented above. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-order-section]: body has extra section(s) --> EIPS/eip-transfer-with-authorization.md | 13 | ## Simple Summary | ::: EIPS/eip-transfer-with-authorization.md | 392 | ## Implementation | = help: see https://ethereum.github.io/eipw/markdown-order-section/

error[markdown-re-eip-dash]: proposals must be referenced with the form `EIP-N` (not `EIPN` or `EIP N`) --> EIPS/eip-transfer-with-authorization.md | 390 | See [EIP3009.test.ts](https://github.com/CoinbaseStablecoin/eip-3009/blob/master/test/EIP3009.test.ts). | = info: the pattern in question: `(?i)eip[\s]*[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-re-eip-dash/

error[markdown-re-eip-dash]: proposals must be referenced with the form `EIP-N` (not `EIPN` or `EIP N`) --> EIPS/eip-transfer-with-authorization.md | 394 | **EIP3009.sol** | = info: the pattern in question: `(?i)eip[\s]*[0-9]+`

error[markdown-re-eip-dash]: proposals must be referenced with the form `EIP-N` (not `EIPN` or `EIP N`) --> EIPS/eip-transfer-with-authorization.md | 468 | **EIP712Domain.sol** | = info: the pattern in question: `(?i)eip[\s]*[0-9]+`

error[markdown-re-eip-dash]: proposals must be referenced with the form `EIP-N` (not `EIPN` or `EIP N`) --> EIPS/eip-transfer-with-authorization.md | 475 | **EIP712.sol** | = info: the pattern in question: `(?i)eip[\s]*[0-9]+`

error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`) --> EIPS/eip-transfer-with-authorization.md | 457 | **IERC20Transfer.sol** | = info: the pattern in question: `(?i)erc[\s]*[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-re-erc-dash/

error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC` --> EIPS/eip-transfer-with-authorization.md | 32 | There is an existing spec, [EIP-2612](./eip-2612), that also allows meta-transactions, and it is encouraged that a contract implements both for maximum compatibility. The two primary differences between this spec and EIP-2612 are that: | = help: see https://ethereum.github.io/eipw/markdown-refs/

Process completed with exit code 1.

Unable to process file command 'env' successfully.

Invalid value. Matching delimiter not found 'EOF'

Canceling since a higher priority waiting request for 'Continuous Integration-8819' exists

The operation was canceled.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/