Process completed with exit code 1.

Unable to process file command 'env' successfully.

Invalid value. Matching delimiter not found 'EOF'

error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7763.md | 16 | This ERC proposes a standard for wallets to generate and manage exposed application-specific key pairs, building upon the concepts introduced in ERC-1775 and complementing ERC-7716. It defines exposed keys that allow free signing by the current site. This approach enhances flexibility in managing permissions for decentralized applications (dApps) while maintaining a balance with security considerations. | = 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-7763.md | 16 | This ERC proposes a standard for wallets to generate and manage exposed application-specific key pairs, building upon the concepts introduced in ERC-1775 and complementing ERC-7716. It defines exposed keys that allow free signing by the current site. This approach enhances flexibility in managing permissions for decentralized applications (dApps) while maintaining a balance with security considerations. | = 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-7763.md | 20 | As the ecosystem of dApps grows, there's an increasing need for more granular and flexible key management. This ERC simplifies the ideas presented in ERC-1775 and ERC-7715 by providing a standard for exposed app keys that a wallet can use to manage permissions for a dApp: | = 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-7763.md | 20 | As the ecosystem of dApps grows, there's an increasing need for more granular and flexible key management. This ERC simplifies the ideas presented in ERC-1775 and ERC-7715 by providing a standard for exposed app keys that a wallet can use to manage permissions for a dApp: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-order-section]: body has extra section(s) --> ERCS/erc-7763.md | 119 | ## Conclusion | = help: see https://ethereum.github.io/eipw/markdown-order-section/

error[markdown-req-section]: body is missing section(s): `Rationale`, `Copyright` --> ERCS/erc-7763.md | | = help: must be at the second level (`## Heading`) = help: see https://ethereum.github.io/eipw/markdown-req-section/

error[preamble-len-title]: preamble header `title` value is too long (max 44) --> ERCS/erc-7763.md:3:7 | 3 | title: Exposed App Keys for Application-Specific Wallet Accounts | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ too long | = help: see https://ethereum.github.io/eipw/preamble-len-title/

error[preamble-re-description]: preamble header `description` should not contain `standard` (or similar words.) --> ERCS/erc-7763.md:4:13 | 4 | description: A standard for generating and managing exposed application-specific key pairs | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ prohibited pattern was matched | = info: the pattern in question: `(?i)standar\w*\b` = help: see https://ethereum.github.io/eipw/preamble-re-description/

validation found errors :(

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