macOS
Homebrewverified · 100%
brew install gitea-runnerlocal Homebrew formula metadata
brew
Install gitea-runner with Homebrew, apk, pacman, winget
Official Actions runner for Gitea. Version 2.0.0 via Homebrew; verified 2026-06-30.
install
Additional install commands
Linux
Alpine Linux apkverified · 92%
sudo apk add gitea-runnerAlpine Linux edge package indexes · gitea-runner · source: dl-cdn.alpinelinux.org
Arch Linux pacmanverified · 92%
sudo pacman -S gitea-runnerArch Linux sync databases · gitea-runner · source: geo.mirror.pkgbuild.com
Windows
Windows Package Managerverified · 92%
winget install --id Gitea.Runner -eWindows Package Manager source index · Gitea.Runner · source: cdn.winget.microsoft.com
overview
Package summary
Official Actions runner for Gitea
Project links
Commands and aliases
- gitea-runner
history
Project history and usage
Gitea Runner is the official runner for Gitea Actions, the workflow automation system used by Gitea installations. It gives self-hosted Gitea sites a worker process that can register with an instance, accept jobs, and execute GitHub Actions-style workflows through Docker or host execution labels.
Project history
The runner codebase descends from the act-runner effort around Gitea Actions. The official repository's Git history begins in 2019 with support for GitHub Actions-style execution, while the Gitea-runner release stream begins with v0.0.1 in 2023 and reaches the renamed Gitea Runner 1.x and 2.x series in 2026.
The project evolved from a companion binary for early Actions support into a documented part of the Gitea platform. Its README and Gitea documentation describe binary, container, Docker-in-Docker, rootless Docker-in-Docker, cache server, label, and post-task-script modes, reflecting the operational concerns of running CI workers for many repositories.
Adoption history
Adoption follows Gitea Actions itself: administrators enable Actions on a Gitea instance, create or obtain runner registration tokens, and attach one or more runner processes to supply build capacity. Packaging in Homebrew, Alpine, Arch, and WinGet makes the runner fit the same self-hosted deployment culture as Gitea.
How it is used
Practitioners use Gitea Runner by generating or supplying a YAML config, registering the runner with a Gitea instance URL and token, then running the daemon. Container deployments often mount the Docker socket or run Docker-in-Docker images so workflow jobs can execute inside job containers.
Labels are central to day-to-day use: a label such as an Ubuntu image or a host execution label controls which workflows can target the runner and how jobs are launched. Operators also configure cache behavior, ephemeral runners, registration state, and cleanup scripts when they need repeatable CI nodes.
Why package nerds care
For package-manager users, Gitea Runner is the small binary that turns a packaged Gitea server from code hosting into a self-contained CI system. It matters because it avoids a separate hosted CI dependency while keeping the workflow syntax close to GitHub Actions.
Timeline
- 2019: Runner repository history begins with GitHub Actions-style execution work.
- 2023: v0.0.1 appears in the runner release stream.
- 2026: v1.0.0 and v2.0.0 mark the renamed Gitea Runner series.
Related projects
- Gitea Runner is closely tied to Gitea, Gitea Actions, workflow files in repositories, and the nektos/act ecosystem that influenced local execution of GitHub Actions workflows.
Sources
security posture
Risk level: orange
formula declares a Homebrew service.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- formula declares a Homebrew service
Signals
- metadata:service
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Formula metadata declares a service or daemon block.
- Homebrew bottle metadata is available for 6 platform targets.
- Build metadata lists 1 build dependencies.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
./config.yaml
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
./.runner
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
gitea-runner | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-07-08
manager version2.0.0
manager updated2026-06-30
local dataok
upstreamnot checked
latest detectednot detected
https://gitea.com/gitea/runner
- infoRelease/tag comparison is only available for GitHub repositories.https://gitea.com/gitea/runnernone confidence
install metadata
Package metadata
| Package key | brew:gitea-runner |
|---|---|
| Version | 2.0.0 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/gitea-runner |
| Homepage | https://gitea.com/gitea/runner |
| Repository | https://gitea.com/gitea/runner |
| Upstream docs | https://docs.gitea.com/usage/actions/act-runner |
| License | MIT |
| Source archive | https://gitea.com/gitea/runner.git |
| Last updated | 2026-06-30T09:48:26Z |
| Pulse | updated |
| Build dependencies | go |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | declared |
| Caveats | Config file: $HOMEBREW_PREFIX/etc/gitea-runner/config.yaml |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | gitea-runner |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
apk95%
gitea-runner 1.0.8-r0
Official runner for Gitea
https://gitea.com/gitea/runner
sudo apk add gitea-runner- License: MIT
- Architecture: x86_64
- Source Package: gitea-runner
- 1 dependencies
- 1 provides
- normalized package name match
- Matched by: Gitea Runner
apk95%
gitea-runner-openrc 1.0.8-r0
Official runner for Gitea (OpenRC init scripts)
https://gitea.com/gitea/runner
sudo apk add gitea-runner-openrc- License: MIT
- Architecture: x86_64
- Source Package: gitea-runner
- normalized package name match
- Matched by: Gitea Runner
pacman95%
gitea-runner 1.0.8-1
Official runner for Gitea
https://gitea.com/gitea/runner
sudo pacman -S gitea-runner- License: MIT
- Architecture: x86_64
- 2 dependencies
- 1 provides
- 1 optional deps
- normalized package name match
- Matched by: Gitea Runner
winget95%
Gitea.Runner
winget install --id Gitea.Runner -e- normalized package name match
- Matched by: Gitea Runner
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment