Issue cards: API works (PATCH /api/v1/.../issues/{idx} {"projects":[id]} — attach to project)
Column moves: only UI drag-and-drop or session-cookie script
Cronjob
See tools/blocked-deps-monitor.py in admin/brencher. Wired as silent cron (no_agent) under Hermes scheduler. Polls hourly, posts alert + drops [blocked/external] title prefix when upstream resolved.
## Upstream blocker
- **Issue:** go-gitea/gitea#14299
- **PR merged:** go-gitea/gitea#38691 (commit `7fae3d5db`, 2026-08-08)
- **What we need:** Gitea v1.28.0 stable release with Projects REST API
## Status
- v1.27.0 (current prod before 11.09): no Projects API
- v1.27.3 (current prod after 11.09): no Projects API (patch-release per SemVer)
- v1.28.0-dev: has Projects API, but dev-указатель, не для prod
- v1.28.0 stable: **not yet released** → blocked
## Tracking
- admin/brencher#63 — main tracking issue
- admin/ansible#37 — step 1 (1.27.3) deployed
- step 2 PR — when 1.28.0 ships
## Workaround until 1.28.0
- Issue cards: API works (`PATCH /api/v1/.../issues/{idx} {"projects":[id]}` — attach to project)
- Column moves: only UI drag-and-drop or session-cookie script
## Cronjob
See `tools/blocked-deps-monitor.py` in `admin/brencher`. Wired as silent cron (`no_agent`) under Hermes scheduler. Polls hourly, posts alert + drops `[blocked/external]` title prefix when upstream resolved.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
Upstream blocker
7fae3d5db, 2026-08-08)Status
Tracking
Workaround until 1.28.0
PATCH /api/v1/.../issues/{idx} {"projects":[id]}— attach to project)Cronjob
See
tools/blocked-deps-monitor.pyinadmin/brencher. Wired as silent cron (no_agent) under Hermes scheduler. Polls hourly, posts alert + drops[blocked/external]title prefix when upstream resolved.🤖 Generated with Claude Code