infra: automatic release tagging

[ibishal]

closes #5863
/claim #5863

[add-deployment-links]

Hey there! Thanks for helping Mudlet improve. 🌟

Test versions

You can directly test the changes here:

• linux: https://make.mudlet.org/snapshots/235c5a/Mudlet-4.17.2-testing-pr7099-a0e5d1ee-linux-x64.AppImage.tar
• osx: (download pending, check back soon!)
• windows: https://make.mudlet.org/snapshots/493148/Mudlet-4.17.2-testing-pr7099-a0e5d1ee-windows.zip

No need to install anything - just unzip and run.
Let us know if it works well, and if it doesn't, please give details.

[vadi2]

Hi! Thanks a lot for this PR. I should have been more clear in the original issue - the file update and tagging should automatically happen off a new Github release (example). The release tag would be the new version that needs to go into mudlet.pro and CMakeLists.txt, and that is what binaries should be built with.

Could you update the PR for that?

[ibishal]

Hi! Thanks a lot for this PR. I should have been more clear in the original issue - the file update and tagging should automatically happen off a new Github release (example). The release tag would be the new version that needs to go into mudlet.pro and CMakeLists.txt, and that is what binaries should be built with.

Could you update the PR for that?

@vadi2 can you check the workflow ig it solve this issue

[vadi2]

Thanks for submitting a PR for this :) we've realised that we need to have a more comprehensive approach to this, so we'll put the automation bounties on hold while we work that out.

Here is a small thanks in the meantime for your efforts!

/tip $10

[algora-pbc]

👉 @vadi2: Navigate to your dashboard to proceed

[algora-pbc]

🎉🎈 @ibishal has been awarded $10! 🎈🎊

• Share on socials
• Give feedback