1.9 KiB
1.9 KiB
Changelog
All notable changes to this project will be documented in this file.
The format follows Keep a Changelog.
[Unreleased]
Added
- Initial repository scaffold: directory structure, Dockerfile, entrypoint, healthcheck, smoke-test, config examples, compose example, and docs.
- Phase 0 planning documents:
AGENT.md,README.md,ROADMAP.md. - First successful local image build:
custom-gitea-runner:v0.1.0(act_runner v0.2.11, Node 20, Docker CLI). Runtime smoke test passes 17/17. - First live registration validated against
git.alwisp.com(Gitea 1.26.4): instance-level runner registers, comes online, runs healthy, and restart reuses the existing config without creating a duplicate.
Fixed
docker/runner/Dockerfile:COPYpaths for the entrypoint, healthcheck, and smoke-test scripts now resolve from the repo-root build context used byscripts/build-image.sh(previously assumed the build context wasdocker/runner/, so the build failed at theCOPYsteps).scripts/verify-runtime.sh: now runs the smoke test via--entrypointso it bypasses thetini/bootstrapENTRYPOINTinstead of triggering the registration flow and failing on a missingGITEA_INSTANCE_URL.docker/runner/docker-entrypoint.sh:GITEA_RUNNER_LABELSis now honored.act_runner registerignores its--labelsflag when a config already exists, so the bootstrap generated a config with default labels and the env var was silently a no-op. The entrypoint now injects the labels into the generated config before registering.scripts/deregister-runner.sh: rewritten to deregister via the Gitea REST API. The previous version calledact_runner daemon --unregister, a flag/command that does not exist in act_runner — deregistration must go throughDELETE /api/v1/admin/actions/runners/{id}. Now takes a runner name or id and an admin API token.