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

renovation

Earl Warren c1892b6398 fix!: fallback to sh if bash does not exist ... It is a breaking change because it changes how the shell is determined. Before, if `jobs.<job_id>.container.image` is set and the shell is not specified, it defaults to `sh` instead of `bash`. After, regardless of `jobs.<job_id>.container.image`, if the shell is not specified, it defaults to `bash` if available, otherwise it defaults to `sh`. Rework the shell integration tests: - Remove container specific tests because the special behavior related to shell being set differently when a container image is present is removed - Modify the defaults test case to verify the fallback logic - Use container images from code.forgejo.org to escape rate limiting in the CI - Add the missing node test - Use container: image: code.forgejo.org/oci/node:22-bookworm instead of container: code.forgejo.org/oci/node:22-bookworm because it silently failed to run (with no exit code) - Prefer `-z "${BASH}"` because `-z ${BASH+x}` reads obscure Closes forgejo/runner#150		2025-07-12 19:01:14 +02:00
act	fix!: fallback to sh if bash does not exist	2025-07-12 19:01:14 +02:00
cmd	[RDNF #16] Fix for issue 2232: Many lines of "Could not find any stages to run" on run (#2272) (#157)	2025-07-02 13:53:35 +00:00
main.go	feat: add check for newer versions (#1562)	2023-01-15 10:30:41 +00:00