Upstream merge 1.14.6 #4349

Annotations

10 errors and 2 warnings

receiver-naming: receiver name c should be consistent with previous receiver name b for BorConfig (revive)

receiver-naming: receiver name c should be consistent with previous receiver name b for BorConfig (revive)

receiver-naming: receiver name c should be consistent with previous receiver name b for BorConfig (revive)

receiver-naming: receiver name mvr should be consistent with previous receiver name res for MVReadResult (revive)

receiver-naming: receiver name api should be consistent with previous receiver name s for BlockChainAPI (revive)

receiver-naming: receiver name api should be consistent with previous receiver name s for BlockChainAPI (revive)

receiver-naming: receiver name api should be consistent with previous receiver name s for BlockChainAPI (revive)

receiver-naming: receiver name p should be consistent with previous receiver name c for StatusCommand (revive)

receiver-naming: receiver name p should be consistent with previous receiver name c for StatusCommand (revive)

receiver-naming: receiver name c should be consistent with previous receiver name b for BootnodeCommand (revive)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. 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 artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "code_10644166069", "logs_10644166069". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/