TheFox0x7 5539ef7275
All checks were successful
checks / build and test (pull_request) Successful in 1m14s
checks / runner exec tests (pull_request) Successful in 1m24s
/ example-docker-compose (pull_request) Successful in 5m32s
/ cascade (pull_request) Has been skipped
add release notes
2024-04-10 23:55:42 +02:00

4.5 KiB

Release Notes



  • Fixes a regression introduced in 3.4.0 by which a job with no image explicitly set would be bound to the host network instead of a custom network (empty string in the configuration file).


Although this version is able to run actions/upload-artifact@v4 and actions/download-artifact@v4, these actions will fail because it does not run against A fork of those two actions with this check disabled is made available at:

and they can be used as shown in an example from the end-to-end test suite.

  • When running against, the default poll frequency is 30s instead of 2s.
  • Fix compatibility issue with actions/{upload,download}-artifact@v4.
  • Upgrade ACT v1.20.0 which brings:
    • [container].options from the config file is exposed in containers created by the workflows
    • the expressions in the value of jobs.<job-id>.runs-on are evaluated
    • fix a bug causing the evaluated expression of jobs.<job-id>.runs-on to fail if it was an array
    • mount act-toolcache:/opt/hostedtoolcache instead of act-toolcache:/toolcache
    • a few improvements to the readability of the error messages displayed in the logs
    • amd64 can be used instead of x86_64 and arm64 intead of aarch64 when specifying the architecture
    • fixed YAML parsing bugs preventing dispatch workflows to be parsed correctly
    • add support for runs-on.labels which is equivalent to runs-on followed by a list of labels
    • the expressions in the service ports and volumes values are evaluated
    • network aliases are only supported when the network is user specified, not when it is provided by the runner
  • If [runner].insecure is true in the configuration, insecure cloning actions is allowed


  • Support IPv6 with addresses from a private range and NAT for docker:// with --enable-ipv6 and [container].enable_ipv6 lxc:// always



The self-hosted label that was hardwired to be a LXC container running debian:bullseye was reworked and documented (user guide and admin guide).

There now are two different schemes: lxc:// for LXC containers and host:// for running directly on the host.

  • Support the host:// scheme for running directly on the host.
  • Support the lxc:// scheme in labels
  • Update v1.14.0 to implement both self-hosted and LXC schemes





  • Publish a rootless OCI image
  • Refactor the release process