The homelab repo was transferred from owner gitea_admin to k.renner. Gitea keeps a 307 redirect for the old path, so git clone/push (which follow redirects over HTTPS) kept working — but the Woodpecker pipelines' curl -sfAPI reads do not follow redirects, so instead of JSON they received the redirect's HTML body and the next jq died with parse error: Invalid numeric literal at line 1, column 3.
Under set -eu this failed the step before any issue or PR was created, which is why every alert-monitor / issue-fix / update-audit / security-scan cron run has been failing and no alert issues were being filed — the alert-triage-agent step crashed right after fetching alerts, before the triage agent ever ran.
Replaced hardcoded gitea_admin/homelab → k.renner/homelab in all API bases, git-push URLs, and cron-add doc comments across alert-monitor.yml, issue-fix.yml, update-audit.yml, security-scan.yml, e2e.yml.
Added -L to the read curls that pipe JSON into jq, so a future rename follows the redirect instead of feeding HTML to jq.
Crons are correctly registered and firing every 15 min; no cron changes needed. 8 alerts were active at the last failed run.
The homelab repo was transferred from owner `gitea_admin` to `k.renner`. Gitea keeps a **307 redirect** for the old path, so `git clone`/`push` (which follow redirects over HTTPS) kept working — but the Woodpecker pipelines' `curl -sf` **API reads do not follow redirects**, so instead of JSON they received the redirect's HTML body and the next `jq` died with `parse error: Invalid numeric literal at line 1, column 3`.
Under `set -eu` this failed the step **before any issue or PR was created**, which is why every `alert-monitor` / `issue-fix` / `update-audit` / `security-scan` cron run has been failing and **no alert issues were being filed** — the `alert-triage-agent` step crashed right after fetching alerts, before the triage agent ever ran.
Verified live: `gitea_admin/homelab` → HTTP 307; `k.renner/homelab` → HTTP 200 with valid JSON.
**What changed**
- Replaced hardcoded `gitea_admin/homelab` → `k.renner/homelab` in all API bases, git-push URLs, and cron-add doc comments across `alert-monitor.yml`, `issue-fix.yml`, `update-audit.yml`, `security-scan.yml`, `e2e.yml`.
- Added `-L` to the read `curl`s that pipe JSON into `jq`, so a future rename follows the redirect instead of feeding HTML to `jq`.
Crons are correctly registered and firing every 15 min; no cron changes needed. 8 alerts were active at the last failed run.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The homelab repo was transferred from owner `gitea_admin` to `k.renner`.
Gitea keeps a 307 redirect for the old path, so git clone/push (which
follow redirects) kept working — but the pipelines' `curl -sf` API reads
do NOT follow redirects, so instead of JSON they received the redirect's
HTML body and the next `jq` died with:
jq: parse error: Invalid numeric literal at line 1, column 3
Under `set -eu` this failed the step before any issue/PR was created,
which is why every alert-monitor / issue-fix / update-audit / security-scan
cron run has been failing and no alert issues were being filed.
- Replace hardcoded `gitea_admin/homelab` -> `k.renner/homelab` in all
API bases, git-push URLs, and cron-add doc comments.
- Add `-L` to the read curls that pipe JSON into jq, so a future rename
degrades gracefully instead of feeding HTML to jq.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The homelab repo was transferred from owner
gitea_admintok.renner. Gitea keeps a 307 redirect for the old path, sogit clone/push(which follow redirects over HTTPS) kept working — but the Woodpecker pipelines'curl -sfAPI reads do not follow redirects, so instead of JSON they received the redirect's HTML body and the nextjqdied withparse error: Invalid numeric literal at line 1, column 3.Under
set -euthis failed the step before any issue or PR was created, which is why everyalert-monitor/issue-fix/update-audit/security-scancron run has been failing and no alert issues were being filed — thealert-triage-agentstep crashed right after fetching alerts, before the triage agent ever ran.Verified live:
gitea_admin/homelab→ HTTP 307;k.renner/homelab→ HTTP 200 with valid JSON.What changed
gitea_admin/homelab→k.renner/homelabin all API bases, git-push URLs, and cron-add doc comments acrossalert-monitor.yml,issue-fix.yml,update-audit.yml,security-scan.yml,e2e.yml.-Lto the readcurls that pipe JSON intojq, so a future rename follows the redirect instead of feeding HTML tojq.Crons are correctly registered and firing every 15 min; no cron changes needed. 8 alerts were active at the last failed run.
🤖 Generated with Claude Code
The homelab repo was transferred from owner `gitea_admin` to `k.renner`. Gitea keeps a 307 redirect for the old path, so git clone/push (which follow redirects) kept working — but the pipelines' `curl -sf` API reads do NOT follow redirects, so instead of JSON they received the redirect's HTML body and the next `jq` died with: jq: parse error: Invalid numeric literal at line 1, column 3 Under `set -eu` this failed the step before any issue/PR was created, which is why every alert-monitor / issue-fix / update-audit / security-scan cron run has been failing and no alert issues were being filed. - Replace hardcoded `gitea_admin/homelab` -> `k.renner/homelab` in all API bases, git-push URLs, and cron-add doc comments. - Add `-L` to the read curls that pipe JSON into jq, so a future rename degrades gracefully instead of feeding HTML to jq. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>