Sorry, I don't think it's a bug of act_runner or Gitea, it is most likely an issue with your local docker environment or network environment.
If you want to seek help, you can ask in QQ group…
I am confused by some comments, this issue is not related to the version of node or the official image.
The point is that when using some actions which have runtime requirements like node env,…
I figured it out - it's not a bug in the act_runner, but rather in the gitea-release-action.
I'll close this one and open actions/gitea-release-action#4
@allen.cai Thank you for pointing out my misunderstanding; I see it now.
GitHub has different execution mechanisms, which may require more work to investigate.
In fact, if you run run: node -v, you will find that Node is not installed in the image, but `actions/che…
Please use ubuntu-latest-full if your disk space is large enough, since the image almost provides the capabilities of GitHub, see https://gitea.com/gitea/runner-images/src/branch/main/README.md#f…
Hmm, I wonder if it's a bug of actions/gitea-release-action since it returns false when exec `echo "any = ${{ contains(github.ref_name, 'alpha')
Sorry, I'm not familiar with the works of packagers. I've never even heard of "Debian's uscan." I would be grateful if you could provide more docs and examples about this.
Never mind, I asked…
Sorry, I don't understand. Why do we need to tag this repo when it's not any type of package and cannot be a dependency? It's totally for gitea/actions-proto-go which has been tagged finely.
DefaultActionToken config
I don't think the code is enough. Could you please explain your design first?
