New package: act-0.2.26

[0x5c]

Testing the changes

• I tested the changes in this PR: YES

New package

• This new package conforms to the quality requirements: YES

[classabbyamp]

adding this adds --version to the act binary (it was very nicely documented, I only found it by looking at the arch pkgbuild):

go_ldflags="-X main.version=${version}"

Would it be good to depend on docker? It may allow for other container backends in the future, but currently it's only docker (nektos/act#303)

[0x5c]

Would it be good to depend on docker? It may allow for other container backends in the future, but currently it's only docker (nektos/act#303)

Yeah, I was thinking of that, just unsure it would be good to add or not. It does say this when docker is not installed/running

failed to obtain container engine info: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I wonder if that is enough indication that docker is needed, by void standards.

The version thing is fixed, thanks for spotting that

[catthehacker]

It may allow for other container backends in the future, but currently it's only docker (nektos/act#303)

It allows for other container backends already, it just needs to have Docker Engine compatible API and connection option, e.g. DOCKER_HOST=unix:///var/run/podman.sock
https://github.com/nektos/act/wiki/Custom-container-engine

[0x5c]

It may allow for other container backends in the future, but currently it's only docker (nektos/act#303)

It allows for other container backends already, it just needs to have Docker Engine compatible API and connection option, e.g. DOCKER_HOST=unix:///var/run/podman.sock
https://github.com/nektos/act/wiki/Custom-container-engine

So it wouldn't be a good idea to add a dependency on docker

--

This PR should be ready to merge