bircni 329115b148 enhance(config): expand environment values (#1274) ...

Config values can reference the runner's environment as `${NAME}`, for example `capacity: ${RUNNER_CAPACITY}`, so container deployments can configure the runner without templating the file. An unset `NAME` fails the load instead of silently becoming empty, and `$${NAME}` writes a literal `${NAME}`. Keys are never expanded.

Breaking: an existing value containing `${NAME}`, such as a shell command in a Kubernetes `pod_template`, now needs `$${NAME}`.

Closes https://gitea.com/gitea/runner/issues/551
Co-authored-by: silverwind <2021+silverwind@noreply.gitea.com>
Co-authored-by: silverwind <me@silverwind.io>
Reviewed-on: https://gitea.com/gitea/runner/pulls/1274
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com>
Co-authored-by: bircni <bircni@icloud.com>

2026-10-08 17:31:00 +00:00

..

builtin-actions.md

fix!: use the git CLI for action clones and make builtin:checkout match actions/checkout (#1277)

2026-10-08 17:08:29 +00:00

job-hooks.md

…

kubernetes.md

enhance(config): expand environment values (#1274)

2026-10-08 17:31:00 +00:00

post-task-script.md

…

telemetry.md

…