It would certainly be more convenient for a user to have access to binaries without having to compile them personally. (At least the more convenient ones like sa2/libretro; and/or the package tarball.)
As an example on how it could be automated, here's how RALibretro configures GitHub to build a RAHasher executable and attach it to a draft release when a tag is pushed. (…I believe it'd also be trivial to limit affected tags by prefix if necessary, via modifying the if: startsWith(github.ref, 'refs/tags/') line; or alternatively limit the build to tags only by moving said line from the step to the job – e.g. after the runs-on: line.)
It would certainly be more convenient for a user to have access to binaries without having to compile them personally. (At least the more convenient ones like sa2/libretro; and/or the package tarball.)
As an example on how it could be automated, here's how RALibretro configures GitHub to build a RAHasher executable and attach it to a draft release when a tag is pushed. (…I believe it'd also be trivial to limit affected tags by prefix if necessary, via modifying the
if: startsWith(github.ref, 'refs/tags/')line; or alternatively limit the build to tags only by moving said line from the step to the job – e.g. after theruns-on:line.)