A few months ago PR #303 was merged, but no artifacts have been built since, I think because tags are not being pushed. I ran git tag -a tag_name -m 'tag_name' and git push origin --follow-tags on the branch I wanted and it worked on my fork. Either that, or the release workflow can be changed to trigger on new release/* branches.
One more thing, I found that for some reason the binary only has -rw------- permissions by default when added to a docker container, I don't know if there needs to be a chmod u+x command in the build or what best practice is.
A few months ago PR #303 was merged, but no artifacts have been built since, I think because tags are not being pushed. I ran
git tag -a tag_name -m 'tag_name'andgit push origin --follow-tagson the branch I wanted and it worked on my fork. Either that, or the release workflow can be changed to trigger on newrelease/*branches.One more thing, I found that for some reason the binary only has
-rw-------permissions by default when added to a docker container, I don't know if there needs to be achmod u+xcommand in the build or what best practice is.