forgejo/runner
33
84
Fork 90
Code Issues 33 Pull requests 10 Releases 80 Packages 1 Activity Actions
80 releases 89 tags
  • v9.0.0 20f115fdac

    v9.0.0
    All checks were successful
    act / unit (push) Successful in 42s
    Details
    checks / build and test (push) Successful in 41s
    Details
    checks / runner exec tests (push) Successful in 29s
    Details
    / example-docker-compose (push) Successful in 1m26s
    Details
    / example-lxc-systemd (push) Successful in 6m48s
    Details
    act / integration (push) Successful in 8m58s
    Details
    Build release / release (push) Has been skipped
    Details
    publish / publish (push) Has been skipped
    Details
    Stable

    release-team released this 2025-07-31 07:10:51 +00:00 | 483 commits to main since this release

    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 at https://example.com/my/repo (a local directory at the root of a Git repository can also be used):

    $ forgejo-runner validate --repository https://example.com/my/repo
.forgejo/workflows/release.yml workflow schema validation OK
.forgejo/workflows/test.yml workflow schema validation OK

    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.

    • features including breaking changes
      • PR: feat!: remove support for using an artifact server via CLI
    • features
      • PR: feat: the new 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. Alternatively forgejo-runner validate --path myaction/action.yml --action or forgejo-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.
      • PR: feat(security): recommend security issues are reported to security@forgejo.org
      • PR: feat(tests): cmd executeCommand captures stderr & stdout
      • PR: feat: merge forgejo/act/pkg in the act directory
    • bug fixes
      • PR: fix: allow expressions in action descriptions and incomplete action inputs
      • PR: fix: the vars context is allowed in an action step env
      • PR: fix: allow expressions in step and job uses:
      • PR: fix(ci): use code.forgejo.org instead of the docker hub
    • other
      • PR: Restore contrib/forgejo-runner.service
      • PR: chore: remove unused/unmaintained files
      • PR: chore: a single testutils for both act and the runner
      • PR: chore: renovate must not look at any testdata subdirectory
      • PR: chore(release-notes): finalize 9.0.0
      • PR: chore: use the act directory instead of https://code.forgejo.org/forgejo/act
      • PR: chore(docs): naked host schema in 8.0.0 is a breaking change
      • PR: chore: disable package name checks for revive [skip cascade]
    Downloads