upload-release-asset VS action-gh-release

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?

While those actions are indeeded archived, they do recommend some other community actions to use. I have used https://github.com/softprops/action-gh-release and it works well. That said, you need to do your own due diligence on how comfortable you are using community actions.

Create a new workflow, and then enter the code below. This code will create the PDF version of the latex file with every push into this repository. Each push will create a new release of your resume's latest iteration, and it will be an artifact attached to this. You may encounter an error based off the permission of the GitHub Action but this issue is explained well in this post.

Alternatively, if you do not want to use the LaTeX compilation process on GitHub Actions, you can omit the building process and track the locally generated PDF file as well. Usually binary files, PDF files in this case, are not tracked. You can remove the Compile LaTeX Document step in the .github/workflows/release.yml file, and start tracking the output PDF in your repository. By this way, you can move the compilation process to local. However, if you follow this path, by default, you will not have your output PDF listed under releases. It is possible to achieve this by editing the Release step in the workflow (see action-gh-release for more information).

I use https://github.com/softprops/action-gh-release to create releases when pull requests happen. But I don't understand how I'm supposed to set tags. The README states this: yml if: startsWith(github.ref, 'refs/tags/')

action-gh-release really makes it easy to do these steps.

softprops/action-gh-release able to achieve that in two lines of code.

Finally, we use a 3rd-party release creation Action for creating a release draft with the release notes and artifacts we just created: