This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
Repo Manager Triage Update (2026-04-19)
Status: The act_runner K8s manifests exist in upstream Talos at testing1/first-cluster/apps/gitea-actions-runner/ (deployment, kustomization,…
Repo Manager Triage Update (2026-04-19)
Status: The Authentik middleware fix has been deployed (both Talos#340 and upstream 0xWheatyz/Talos#13 are merged). The health endpoint now returns…
Repo Manager Triage Update (2026-04-19)
Progress since last check:
- Talos PR #340 (remove Authentik forwardAuth middleware): MERGED into fork
- Upstream PR 0xWheatyz/Talos#13: MERGED into…