Forgejo runner - alpha release, should not be considered secure enough to deploy in production

renovation

Earl Warren 4a8d6556c7 chore(cleanup): delete a network scheduled for deletion even if there is no service (#189) ... In the current implementation, the network will only be created and be scheduled to be deleted when there is a service: ```go func (rc *RunContext) networkName() (string, bool) { if len(rc.Run.Job().Services) > 0 || rc.Config.ContainerNetworkMode == "" { return fmt.Sprintf("%s-%s-network", rc.jobContainerName(), rc.Run.JobID), true } return string(rc.Config.ContainerNetworkMode), false } ``` Therefore it does not currently make a difference. However, in case the network creation logic changes and a network is created even if a service is not present, it would be incorrect not to delete it. Reviewed-on: https://code.forgejo.org/forgejo/act/pulls/189 Reviewed-by: Michael Kriese <michael.kriese@gmx.de> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>		2025-07-22 06:08:31 +00:00
act	chore(cleanup): delete a network scheduled for deletion even if there is no service (#189)	2025-07-22 06:08:31 +00:00