Automic VaultAutomic Vault

brew

Installer gitea-runner avec Homebrew, apk, pacman, winget

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de gitea-runner pour les workflows d'agents IA.

Commande d'installationNotes de sécurité

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install gitea-runner

local Homebrew formula metadata

Windows

Windows Package Managervérifié · 92%
winget install --id Gitea.Runner -e

Windows Package Manager source index · Gitea.Runner · Source: cdn.winget.microsoft.com

aperçu

Résumé du paquet

Official Actions runner for Gitea

Commandes et alias

  • gitea-runner

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : orange

formula declares a Homebrew service.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • formula declares a Homebrew service

Signaux

  • metadata:service

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de formule déclarent un service ou daemon.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des 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

exécutables

Exécutables installés

CommandeTypeExpositionNote
gitea-runnercliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire2.2.0
gestionnaire mis à jour2026-07-23
données localesOK
amontnot checked
dernière version détectéenon détecté

https://gitea.com/gitea/runner

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:gitea-runner
Version2.2.0
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/gitea-runner
Page d'accueilhttps://gitea.com/gitea/runner
Dépôthttps://gitea.com/gitea/runner
Docs amonthttps://docs.gitea.com/usage/actions/act-runner
LicenceMIT
Archive sourcehttps://gitea.com/gitea/runner/archive/v2.2.0.tar.gz
Dernière mise à jour2026-07-23T01:22:13Z
Pulseupdated
Dépendances de compilationgo
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Servicedeclared
PrécautionsConfig file: $HOMEBREW_PREFIX/etc/gitea-runner/config.yaml

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegitea-runner
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

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 Dépendances
  • 1 fournit
  • normalized package name match
  • Correspondance par : Gitea Runner
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: gitea-runner from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
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
  • Correspondance par : Gitea Runner
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: gitea-runner-openrc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
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 Dépendances
  • 1 fournit
  • 1 dépendances optionnelles
  • normalized package name match
  • Correspondance par : Gitea Runner
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: gitea-runner from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
winget95%

Gitea.Runner

winget install --id Gitea.Runner -e
  • normalized package name match
  • Correspondance par : Gitea Runner
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Gitea.Runner from https://cdn.winget.microsoft.com/cache/source.msix

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

Outils liés

  • goBuild dependency declared by Homebrew.
  • gitea-mcp-serverPackage names and metadata indicate a similar tool family. Shared terms: cli, gitea.
  • giteaPackage names and metadata indicate a similar tool family. Shared terms: ci-cd, cli, developer, developer-tools, gitea.

Même workflow

  • bitriseShares av.db curated category or tags: automation, ci-cd, cli, developer-tools.
  • daggerShares av.db curated category or tags: automation, ci-cd, cli, developer-tools.
  • gitlab-runnerShares av.db curated category or tags: automation, cli, developer-tools, runner.
  • jenkins-job-builderShares av.db curated category or tags: automation, ci-cd, cli, developer-tools.
  • pipelightShares av.db curated category or tags: automation, ci-cd, cli, developer-tools.
  • tfcmtShares av.db curated category or tags: automation, ci-cd, cli, developer-tools.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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