-
Add runner capability detection and reporting
Some checks failedrelease-nightly / release-image (map[tag_suffix: target:basic]) (push) Failing after 0srelease-nightly / release-image (map[tag_suffix:-dind-rootless target:dind-rootless]) (push) Failing after 0srelease-tag / goreleaser (push) Failing after 2srelease-tag / release-image (push) Failing after 0schecks / check and test (push) Failing after 2srelease-nightly / goreleaser (push) Failing after 3srelease-nightly / release-image (map[tag_suffix:-dind target:dind]) (push) Failing after 0sreleased this
2026-01-10 09:49:54 +00:00 | 12 commits to main since this releaseThis change adds automatic detection of runner capabilities including:
- OS and architecture
- Docker/Podman availability and version
- Docker Compose support
- Available shells (bash, sh, pwsh, etc.)
- Installed development tools (Node, Go, Python, Java, .NET, Rust)
- Feature support flags (cache, services, composite actions)
- Known limitations (artifact v4 not supported)
Capabilities are detected on startup and sent to Gitea via the
CapabilitiesJson field in DeclareRequest. This enables AI tools
to query runner capabilities before generating workflows.Uses GitCaddy fork of actions-proto-go with capability support.
🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.5 noreply@anthropic.com
Source Code