RadarKit VS upload-release-asset

The Radar Kit allows you to locate places and trips nearby you, or it will help you to search out the people around you with a few lines of code..!!!

For more detail, visit this repo: https://github.com/Mindinventory/RadarKit

is it possible to write a GitHub Action that would compile my Rust binary for 3 different systems (Mac, Linux and Windows), create a new release on GitHub and upload those binaries to it? I've found this action, and also this one. Those seem to be able to do what I need, but they are both archived and not actively maintained for quite a while. Is it even safe to use those? I know that Actions can be used to compile my binaries as I've already been using them to run tests on all three systems, but I want to know if it is possible upload those binaries and create release with them. Also, is it possible to read version number from a file in my repository with GitHub Actions to set that as a name for a new release?

Call upload-release-asset to upload zip asset to the release (to be used by publish-on-chrome-web-store and publish-on-firefox-add-ons workflows later).

All 3 steps use the same upload-release-asset action to add an asset to the release by its upload_url extracted from createRelease step's output. To provide asset_path we use outputs of corresponding steps which contain absolute path to artifacts.

I followed the instructions on the upload-release-asset action, but never got it to work. Has anyone else got it working, so I can have a look at their .github-actions.yml?