client v0.40.1 release

[github-actions]

Requirements

• fix: support runtime api Core::initialize_block for old runtimes #2959
• Ready for release

Pre-Release

• Create branch perm-v0.40.1 against previous client git tag.
• In the branch perm-v0.40.1, bump client version to v0.40.1.

Release

• Tag perm-v0.40.1 with v0.40.1 and push to github.
• Start the github action Publish Binary Draft with v0.40.0 => v0.40.1
  (master branch).
  • gh workflow run "Publish Binary Draft" -r 'master' -f from=runtime-v0.40.0 -f to=runtime-v0.40.1
• Review the generated Draft and clean a bit the messages if needed (keep it draft).
• Update moonbeam-networks stagenet (moonsama/moonlama) config.json to include:

  "binaries": [
    {
      "docker": "moonbeamfoundation/moonbeam:v0.40.1-rc",
      "path": "/moonbeam/moonbeam",
      "name": "moonbeam"
    },
    {
      "docker": "moonbeamfoundation/moonbeam:v0.40.1-rc",
      "path": "/moonbeam/moonbeam-skylake",
      "name": "moonbeam-skylake"
    }
  ]

(matching your v0.40.1 tag) and increase the config version + 1.

• Test the new client on stagenet (moonsama/moonlama).
• Publish the client release draft.
• When everything is ok, publish the new docker image: start github action Publish Docker
  with v0.40.1.
• Publish the new tracing image: on repo moonbeam-runtime-overrides, start github action
  Publish Docker with v0.40.1 and master.

[RomarQ]

I think there is some issue with the docker image for arm64. Cannot pull v0.40.1 on my machine, but can pull v0.40.0.

[noandrea]

🤔 can you try pulling v0.40.1-rc ?

[RomarQ]

🤔 can you try pulling v0.40.1-rc ?

Same error: no matching manifest for linux/arm64/v8 in the manifest list entries