error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-7766.md | 64 | This EIP inherits the ERC-721 NFT token standard for all transfer and approval logic. All transfer and approval functions are inherited from this token standard without changes. Additionally, this EIP also inherits the ERC-721 Metadata standards for name, symbol, and metadata URI lookup. | = 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-7766.md | 64 | This EIP inherits the ERC-721 NFT token standard for all transfer and approval logic. All transfer and approval functions are inherited from this token standard without changes. Additionally, this EIP also inherits the ERC-721 Metadata standards for name, symbol, and metadata URI lookup. | = 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-7766.md | 131 | The **metadata extension** is OPTIONAL for ERC-7766 smart contracts. This allows your smart contract to be interrogated for its details about the privileges which your NFTs carry. | = 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-7766.md | 149 | This is the “ERC-7766 Metadata JSON Schema” referenced above. | = 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-7766.md | 206 | This standard is an extension of EIP-721. It is fully compatible with both of the commonly used optional extensions (IERC721Metadata and IERC721Enumerable) mentioned in the EIP-721 standard. | = 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-7766.md | 206 | This standard is an extension of EIP-721. It is fully compatible with both of the commonly used optional extensions (IERC721Metadata and IERC721Enumerable) mentioned in the EIP-721 standard. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`) --> EIPS/eip-7766.md | 191 | 6. IERC7766Metadata provides specifications for obtaining metadata information of privileges. A contract that implements IERC7766Metadata **SHALL** also implement IERC7766. | = info: the pattern in question: `(?i)erc[\s]*[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-re-erc-dash/

error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`) --> EIPS/eip-7766.md | 191 | 6. IERC7766Metadata provides specifications for obtaining metadata information of privileges. A contract that implements IERC7766Metadata **SHALL** also implement IERC7766. | = info: the pattern in question: `(?i)erc[\s]*[0-9]+`

error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`) --> EIPS/eip-7766.md | 206 | This standard is an extension of EIP-721. It is fully compatible with both of the commonly used optional extensions (IERC721Metadata and IERC721Enumerable) mentioned in the EIP-721 standard. | = info: the pattern in question: `(?i)erc[\s]*[0-9]+`

error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC` --> EIPS/eip-7766.md | 206 | This standard is an extension of EIP-721. It is fully compatible with both of the commonly used optional extensions (IERC721Metadata and IERC721Enumerable) mentioned in the EIP-721 standard. | = help: see https://ethereum.github.io/eipw/markdown-refs/

EIPS/eip-7766.md:150 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```"]

Failed with exit code: 1

Canceling since a higher priority waiting request for 'Continuous Integration-8861' 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/

warning[markdown-html-comments]: HTML comments are only allowed while `status` is one of: `Draft`, `Withdrawn` --> EIPS/eip-7766.md | 13 | <!-- | ::: EIPS/eip-7766.md | 27 | <!-- | ::: EIPS/eip-7766.md | 37 | <!-- | ::: EIPS/eip-7766.md | 54 | <!-- | ::: EIPS/eip-7766.md | 173 | <!-- | ::: EIPS/eip-7766.md | 195 | <!-- | ::: EIPS/eip-7766.md | 210 | <!-- | ::: EIPS/eip-7766.md | 223 | <!-- | = help: see https://ethereum.github.io/eipw/markdown-html-comments/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f, DavidAnson/markdownlint-cli2-action@f5cf187ef11bd3a68a127321b794aa252ff23019. 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/