Bumps the Gitea stack image from 1.27.0 to 1.27.3 — the last stable release on the 1.27.x line.
This is the first PR in a two-step plan tracked in admin/brencher#63:
This PR — bump to 1.27.3. Stable, security patches only, no schema change, no Projects API yet. Goal: validate the upgrade path (DB migration, container swap, compose-version label update) without introducing new features.
Follow-up PR (planned) — bump to 1.28.0 (or build from main) once 1.28.x ships with the Projects REST API landed in 7fae3d5db (merged 2026-08-08).
Why 1.27.0 is insufficient
Gitea 1.27.0 was released 2026-07-13. Three weeks later, on 2026-08-08, silverwind merged PR go-gitea/gitea#38691 — the long-awaited Projects REST API (the resolution of go-gitea/gitea#14299, originally filed in 2019). That commit (7fae3d5db) added full CRUD for repo/org/user project boards, columns, and issue↔column assignment.
The current prod instance at gitea.rudolf.keenetic.link reports 1.27.0, which is why we cannot move kanban cards programmatically today (verified end-to-end in admin/brencher#63's repro section).
Why stop at 1.27.3 (not jump straight to 1.28.0)
1.27.3 is the last stable 1.27.x and contains the SECURITY fix for CVE-2024-45337 (access-token scope bypass) plus 8 months of bug fixes — strictly safer than staying on 1.27.0.
1.28.0 is not yet released as of writing (only v1.28.0-dev exists on the upstream tag list, dated 2026-06-29 — before the Projects API merge). Going to :dev or :main would require a build pipeline we don't have today and would skip the version bump validation path. The Projects API change also adds a column to project_board (per #37701 migration v333), so the jump is a real schema change that should be its own validated step.
## Summary
Bumps the Gitea stack image from `1.27.0` to `1.27.3` — the last stable release on the 1.27.x line.
This is the first PR in a two-step plan tracked in admin/brencher#63:
1. **This PR** — bump to `1.27.3`. Stable, security patches only, no schema change, no Projects API yet. Goal: validate the upgrade path (DB migration, container swap, compose-version label update) without introducing new features.
2. **Follow-up PR (planned)** — bump to `1.28.0` (or build from `main`) once `1.28.x` ships with the Projects REST API landed in `7fae3d5db` (merged 2026-08-08).
## Why 1.27.0 is insufficient
Gitea `1.27.0` was released 2026-07-13. Three weeks later, on 2026-08-08, `silverwind` merged PR go-gitea/gitea#38691 — the long-awaited Projects REST API (the resolution of go-gitea/gitea#14299, originally filed in 2019). That commit (`7fae3d5db`) added full CRUD for repo/org/user project boards, columns, and issue↔column assignment.
1.27.0 ships **before** that merge. Confirmed:
- `git ls-tree v1.27.0 --name-only | grep routers/api/v1/.*project` → empty.
- `git ls-tree 7fae3d5db --name-only | grep project` → `routers/api/v1/shared/project.go`, `routers/api/v1/swagger/project.go`, and routes registered inside `routers/api/v1/api.go` (`addProjectRoutes`).
The current prod instance at `gitea.rudolf.keenetic.link` reports `1.27.0`, which is why we cannot move kanban cards programmatically today (verified end-to-end in admin/brencher#63's repro section).
## Why stop at 1.27.3 (not jump straight to 1.28.0)
1.27.3 is the last stable 1.27.x and contains the SECURITY fix for CVE-2024-45337 (access-token scope bypass) plus 8 months of bug fixes — strictly safer than staying on 1.27.0.
1.28.0 is not yet released as of writing (only `v1.28.0-dev` exists on the upstream tag list, dated 2026-06-29 — before the Projects API merge). Going to `:dev` or `:main` would require a build pipeline we don't have today and would skip the version bump validation path. The Projects API change also adds a column to `project_board` (per #37701 migration `v333`), so the jump is a real schema change that should be its own validated step.
## Diff
```
- image: docker.gitea.com/gitea:1.27.0
+ image: docker.gitea.com/gitea:1.27.3
```
## Validation after deploy
| Check | Expected |
|-------|----------|
| `GET /api/v1/version` | `1.27.3` |
| `POST /api/v1/repos/{owner}/{repo}/issues` | `201` |
| `PATCH /api/v1/repos/{owner}/{repo}/issues/{idx} {"projects":[id]}` | `200` with updated projects |
| WebSocket /ws uptime (admin/brencher#58 regression check) | no new KeyError |
| Stack `gitea_server` compose-version label | `auto-1.27.3-*` |
| Existing orgs / repos / users | unchanged (DB upgrade path is forward-compatible within 1.27.x) |
## Risk
Low. 1.27.x → 1.27.3 is a patch-level bump. No migrations required beyond what 1.27.0 → 1.27.3 already covers upstream. Existing tokens, repos, projects, kanban cards, comments, and access controls are unaffected.
## Refs
- Tracking: admin/brencher#63
- Closed upstream feature request: go-gitea/gitea#14299
- Closed upstream agentic-workflows request: go-gitea/gitea#37151
- Projects API merge commit: go-gitea/gitea@7fae3d5db (PR #38691)
- 1.27.3 release notes: go-gitea/gitea/releases/tag/v1.27.3
- CVE-2024-45337: go-gitea/gitea/security/advisories/GHSA-7hqw-9c4g-2v25
🤖 Generated with [Claude Code](https://claude.com/claude-code)
First step of admin/brencher#63 — staging the Gitea upgrade path on
the stable 1.27.x line. 1.27.3 includes the SECURITY fix for CVE-2024-45337
(Gitea access token scope bypass) and several other fixes shipped since
1.27.0. It does NOT yet include the Projects REST API (admin/brencher#63
also tracks the eventual 1.28 bump for that).
This is the conservative pre-flight: bumping to the last 1.27.x stable
first lets the DB-migration path be validated before we attempt the
larger jump to 1.28.0 (which adds the new project_board column from
go-gitea/gitea commit 7fae3d5db3df8996f39b2b4ce4435158c5c54b66).
Validation after deploy:
- POST /api/v1/repos/{owner}/{repo}/issues still returns 201
- PATCH /api/v1/repos/{owner}/{repo}/issues/{idx} {"projects":[id]} still works
- /admin/brencher#58 stays green (ws_connections race fix still holds)
- existing compose-version label on stack "gitea_server" updates to auto-1.27.3-*
Refs: admin/brencher#63, https://github.com/go-gitea/gitea/issues/14299,
https://github.com/go-gitea/gitea/commit/7fae3d5db3df8996f39b2b4ce4435158c5c54b66,
https://github.com/go-gitea/gitea/releases/tag/v1.27.3
Step 1 of admin/brencher#63 — bumps to 1.27.3 (stable, last 1.27.x). Step 2 (1.28.0 with Projects API from go-gitea/gitea@7fae3d5db) will follow once 1.28.0 ships.
Step 1 of admin/brencher#63 — bumps to 1.27.3 (stable, last 1.27.x). Step 2 (1.28.0 with Projects API from go-gitea/gitea@7fae3d5db) will follow once 1.28.0 ships.
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.
Summary
Bumps the Gitea stack image from
1.27.0to1.27.3— the last stable release on the 1.27.x line.This is the first PR in a two-step plan tracked in admin/brencher#63:
1.27.3. Stable, security patches only, no schema change, no Projects API yet. Goal: validate the upgrade path (DB migration, container swap, compose-version label update) without introducing new features.1.28.0(or build frommain) once1.28.xships with the Projects REST API landed in7fae3d5db(merged 2026-08-08).Why 1.27.0 is insufficient
Gitea
1.27.0was released 2026-07-13. Three weeks later, on 2026-08-08,silverwindmerged PR go-gitea/gitea#38691 — the long-awaited Projects REST API (the resolution of go-gitea/gitea#14299, originally filed in 2019). That commit (7fae3d5db) added full CRUD for repo/org/user project boards, columns, and issue↔column assignment.1.27.0 ships before that merge. Confirmed:
git ls-tree v1.27.0 --name-only | grep routers/api/v1/.*project→ empty.git ls-tree 7fae3d5db --name-only | grep project→routers/api/v1/shared/project.go,routers/api/v1/swagger/project.go, and routes registered insiderouters/api/v1/api.go(addProjectRoutes).The current prod instance at
gitea.rudolf.keenetic.linkreports1.27.0, which is why we cannot move kanban cards programmatically today (verified end-to-end in admin/brencher#63's repro section).Why stop at 1.27.3 (not jump straight to 1.28.0)
1.27.3 is the last stable 1.27.x and contains the SECURITY fix for CVE-2024-45337 (access-token scope bypass) plus 8 months of bug fixes — strictly safer than staying on 1.27.0.
1.28.0 is not yet released as of writing (only
v1.28.0-devexists on the upstream tag list, dated 2026-06-29 — before the Projects API merge). Going to:devor:mainwould require a build pipeline we don't have today and would skip the version bump validation path. The Projects API change also adds a column toproject_board(per #37701 migrationv333), so the jump is a real schema change that should be its own validated step.Diff
Validation after deploy
GET /api/v1/version1.27.3POST /api/v1/repos/{owner}/{repo}/issues201PATCH /api/v1/repos/{owner}/{repo}/issues/{idx} {"projects":[id]}200with updated projectsgitea_servercompose-version labelauto-1.27.3-*Risk
Low. 1.27.x → 1.27.3 is a patch-level bump. No migrations required beyond what 1.27.0 → 1.27.3 already covers upstream. Existing tokens, repos, projects, kanban cards, comments, and access controls are unaffected.
Refs
🤖 Generated with Claude Code
Step 1 of admin/brencher#63 — bumps to 1.27.3 (stable, last 1.27.x). Step 2 (1.28.0 with Projects API from go-gitea/gitea@7fae3d5db) will follow once 1.28.0 ships.
Step 1 of admin/brencher#63 — bumps to 1.27.3 (stable, last 1.27.x). Step 2 (1.28.0 with Projects API from go-gitea/gitea@7fae3d5db) will follow once 1.28.0 ships.