error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 22 | 3. How to detect if a contract implements ERC-165 | = 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 --> ERCS/erc-165.md | 57 | A contract that is compliant with ERC-165 shall implement the following interface (referred as `ERC165.sol`): | = 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 --> ERCS/erc-165.md | 86 | ### How to Detect if a Contract Implements ERC-165 | = 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 --> ERCS/erc-165.md | 89 | 2. If the call fails or return false, the destination contract does not implement ERC-165. | = 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 --> ERCS/erc-165.md | 91 | 4. If the second call fails or returns true, the destination contract does not implement ERC-165. | = 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 --> ERCS/erc-165.md | 92 | 5. Otherwise it implements ERC-165. | = 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 --> ERCS/erc-165.md | 96 | 1. If you are not sure if the contract implements ERC-165, use the above procedure to confirm. | = 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 --> ERCS/erc-165.md | 97 | 2. If it does not implement ERC-165, then you will have to see what methods it uses the old-fashioned way. | = 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 --> ERCS/erc-165.md | 98 | 3. If it implements ERC-165 then just call `supportsInterface(interfaceID)` to determine if it implements an interface you can use. | = 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 --> ERCS/erc-165.md | 106 | The mechanism described above (with `0xffffffff`) should work with most of the contracts previous to this standard to determine that they do not implement ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

Process completed with exit code 1.

Unable to process file command 'env' successfully.

Invalid value. Matching delimiter not found 'EOF'

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.