mirror of
https://code.forgejo.org/forgejo/runner.git
synced 2024-11-27 07:53:01 +03:00
4.1 KiB
4.1 KiB
Release Notes
3.4.1
- 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).
3.4.0
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 GitHub.com. A fork of those two actions with this check disabled is made available at:
- https://code.forgejo.org/forgejo/upload-artifact/src/tag/v4
- https://code.forgejo.org/forgejo/download-artifact/src/tag/v4
and they can be used as shown in an example from the end-to-end test suite.
- When running against codeberg.org, 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 ofact-toolcache:/toolcache
- a few improvements to the readability of the error messages displayed in the logs
amd64
can be used instead ofx86_64
andarm64
intead ofaarch64
when specifying the architecture- fixed YAML parsing bugs preventing dispatch workflows to be parsed correctly
- add support for
runs-on.labels
which is equivalent toruns-on
followed by a list of labels - the expressions in the service
ports
andvolumes
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
3.3.0
- Support IPv6 with addresses from a private range and NAT for docker:// with --enable-ipv6 and [container].enable_ipv6 lxc:// always
3.2.0
- Support LXC container capabilities via
lxc:lxc://debian:bookworm:k8s
orlxc:lxc://debian:bookworm:docker lxc k8s
- Update ACT v1.16.0 to resolve a race condition when bootstraping LXC templates
3.1.0
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 code.forgejo.org/forgejo/act v1.14.0 to implement both self-hosted and LXC schemes
3.0.3
- Update code.forgejo.org/forgejo/act v1.13.0 to keep up with github.com/nektos/act
3.0.2
- Update code.forgejo.org/forgejo/act v1.12.0 to upgrade the node installed in the LXC container to node20
3.0.1
- Update code.forgejo.org/forgejo/act v1.11.0 to resolve a bug preventing actions based on node20 from running, such as checkout@v4.
3.0.0
- Publish a rootless OCI image
- Refactor the release process
2.5.0
2.4.0
2.3.0
- Add support for offline registration.