B. Yap

All the scripts have been moved to gitlab.

@TorstenStueber > Some major missing part is of course the creation of a GitHub release but I assume that you will add this to the GitLab CI flow? Yes, I'll...

@ebma, I "resolved" the conversations but the `Squash and merge` button is still disabled. Can you try to "resolve" them and see if it works?

> ### Running in standalone mode > To run: It would be nice to have this _how-to_ at the bottom of the README.md. :ok_hand:

@gianfra-t Yes. Ideally after this workflow, it would be great to create a tag and then the release notes (which will be in gitlab, as is our practice). But I...

@ebma @gianfra-t From what I remember, Node upgrade is independent from the runtime release, and should be performed on **all** runtimes. https://satoshipay.slack.com/archives/C047E2XQ160/p1710232364946679 We have never defined "foucoco release"; what's the...

@ebma We can definitely follow moonbeam. I'll check their workflow and update this PR next week.

@ebma @TorstenStueber We'll need @zoveress to setup the release on gitlab. I've setup the get_commit.sh, similar to the `runtime-upgrade-automation`. We just have to decide the assets to attach; * pendulum-node...

@bobo-k2 @gtg7784 Should I send test tokens to both accounts: `XLoLJBQoMPHMLXYhdFobSpH5GujRoUH8d1sUtaEtoBG7zaS` `WGeDwTxHVMnbzNS7xkKsxfrabvimPkF96eBa7uYYbTDzNiG` ? Or any of these 2?

@gtg7784 XLM tokens transferred: https://pendulum.subscan.io/xcm_message/polkadot-a01b30d8091ec0b61088d9ca2550049e55ba3bcc https://pendulum.subscan.io/xcm_message/polkadot-3bb12bfa4fdb443eb5d38f444236875a33a10c84