Update code.forgejo.org/forgejo/runner Docker tag to v9 - autoclosed #256
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/code.forgejo.org-forgejo-runner-9.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.0.0
->9.1.1
Release Notes
forgejo/runner (code.forgejo.org/forgejo/runner)
v9.1.1
Compare Source
Release Notes
v9.1.0
Compare Source
Release Notes
[runner].timeout
expiresshell
on a task step if it referenced a matrix variablev9.0.3
Compare Source
Release Notes
job.<id>.services.<id>.options
v9.0.2
Compare Source
v9.0.1
Compare Source
v9.0.0
Compare Source
Workflows and actions go through a schema validation and the runner will not start a job if they do not pass. Some existing workflows or actions may have syntax errors that did not prevent them from running with versions 7.0.0 and below but they will no longer work with versions 8.0.0 and above.
Existing workflows can be verified and fixed before upgrading by using the new
forgejo-runner validate
command. For instance, the following will try to validate workflows and/or actions found in the Git repository athttps://example.com/my/repo
(a local directory at the root of a Git repository can also be used):If the error is not immediately obvious, please file an issue with a copy of the failed workflow and revert to using version 7.0.0 until it is resolved.
forgejo-runner validate
command can be used to verify if an action or a workflow is conformant with the expected schema.forgejo-runner validate --repository https://example.com/my/repository
will validate all the workflows and actions a Git repository contains. Alternativelyforgejo-runner validate --path myaction/action.yml --action
orforgejo-runner validate --path .forgejo/workflows/test.yml --workflow
can be used to validate a single file. It is recommended to use these commands to verify existing actions and workflows pass before upgrading to Forgejo runner v8.0.0 or above to not disrupt existing workflows.contrib/forgejo-runner.service
host
schema in 8.0.0 is a breaking changev8.0.1
Compare Source
v8.0.0
Compare Source
Existing workflows can be verified and fixed before upgrading by using
forgejo-runner exec --workflows path-to-the-workflow
. For instance in a workflow whereruins-on
was typed by mistake instead ofruns-on
: If the error is not immediately obvious, please file an issue with a copy of the failed workflow and revert to using version 7.0.0 until it is resolved.docker://node:22-bookworm
instead ofdocker://node:20-bullseye
orhost
.lxc
scheme is set with no argument, it defaults tolxc://debian:bookworm
instead oflxc://debian:bullseye
.host
schema cannot have any argument, it can no longer behost://-self-hosted
bash
instead ofsh
when a container image is explicitly specified in the step. If a workflow depens on that behavior, it will need to be modified to explictly set the shell tosh
.[^A-Z0-9-]+
. They will be sanitized and a message displayed in the logs showing the sanitized name. The service can either be renamed to match the constraint so it can be used as is. Or the sanitized name can be used. For instance of a PostgreSQL service runs asdata.base
it will be sanitized asdata_base
.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
17cf2fd841
toee272be194
ee272be194
to08925d2974
08925d2974
to7ad113ca12
7ad113ca12
toc8e35fd7a8
c8e35fd7a8
tod70f44f9cb
Update code.forgejo.org/forgejo/runner Docker tag to v9to Update code.forgejo.org/forgejo/runner Docker tag to v9 - autoclosedPull request closed