[infra] Upgrade Gitea to 1.28.0 (or current main) to enable Projects API #63

Open
opened 2026-09-12 10:52:15 +02:00 by hermes · 3 comments
Contributor

Status

  • Tracking issue open
  • PR open
  • Gitea upgrade deployed
  • Projects API verified
  • Issue #3 moved via API to In Progress column
  • Closed

Goal

Self-hosted Gitea at https://gitea.rudolf.keenetic.link/ is currently running version 1.27.0, which does NOT include the Projects REST API. Agentic workflows (kanban automation, CI integrations, MCP-style tooling) cannot programmatically move issues between Kanban columns on 1.27.0 — only drag-and-drop in the UI works.

Why 1.27.0 is broken for Projects API

  • https://github.com/go-gitea/gitea/issues/14299 ("API for projects") — closed via PR #38691 on 2026-08-08 (commit 7fae3d5db3df8996f39b2b4ce4435158c5c54b66).
  • That PR added full REST API for project boards (repo, org, user scopes) — list, create, get, update, delete projects; list/create/get/update/delete columns; issue-to-column assignment, column moves, reorder. ~1500 lines of code + swagger. All behind the same token scopes as the rest of the API.
  • routers/api/v1/shared/project.go and routers/api/v1/swagger/project.go did not exist on 1.27.0 (verified via git ls-tree v1.27.0 --name-only | grep project → empty).
  • Current Gitea 1.27.0 instance at gitea.rudolf.keenetic.link ships before this commit.

What landed and where

Tag Date Has Projects API?
v1.27.0 2026-07-13 ❌ no
v1.27.1 2026-07-27 ❌ no
v1.27.2 2026-08-13 needs verification (5 days after #38691 merge, but no explicit projects file in shallow listing)
v1.27.3 2026-08-29 needs verification
v1.28.0-dev post-2026-08-29 ✅ yes (commit 7fae3d5db reachable in main)
main today ✅ yes

The PR #38691 is currently reachable only on main and v1.28.0-dev. No release tag yet contains it.

Reference issues and PRs

Repro / current state

  1. Create an Org1/Test1 issue (works via API).
  2. POST /api/v1/repos/Org1/Test1/issues — works.
  3. PATCH /api/v1/repos/Org1/Test1/issues/{idx} {"projects": [4]} — works (attach issue to project).
  4. POST /Org1/Test1/issues/{idx}/projects/column — 404 (web route requires session cookie, basic auth is API-only — see services/auth/basic.go:35).
  5. POST /api/v1/orgs/Org1/projects/4/columns/{id}/cards — 404 page not found (the entire routers/api/v1/org/projects.go file does not exist in 1.27.0).
  6. Drag-and-drop in UI works as expected.

Currently issue Org1/Test1#3 is bound to project Org1/projects#4 (Proj1) but sits in the default column (Backlog, id=10) because the agent cannot move it via API.

Plan

  1. Upgrade the Gitea instance to a build containing 7fae3d5db (either track main or build a release that ships the PR).
  2. Verify with a minimal smoke test against /api/v1/orgs/{org}/projects — must return 200 with the existing Proj1 payload.
  3. Re-run the move test: POST /api/v1/orgs/Org1/projects/4/columns/12/cards {"issue_id": 3} — should now return 200/201.
  4. Migrate any existing tracking workflows that depended on title-prefix status to use the new Projects API endpoints.
  5. Close this issue.

Risk

Upgrading Gitea across a minor version (1.27 → 1.28) requires a database migration. The migration that ships with 7fae3d5db adds a column to project_board — should be reviewed before applying. Snapshot the Gitea DB before upgrade.

Related admin/brencher context

  • Self-hosted Gitea at gitea.rudolf.keenetic.link runs in stack gitea (admin/gitea).
  • brencher deploys compose files from admin/ansible repo via brencher bot (not via Gitea APIs).
  • The Gitea upgrade is performed out-of-band from brencher (Docker image swap + DB migration).

🤖 Generated with Claude Code

## Status - [x] Tracking issue open - [x] PR open - [ ] Gitea upgrade deployed - [ ] Projects API verified - [ ] Issue #3 moved via API to In Progress column - [ ] Closed ## Goal Self-hosted Gitea at `https://gitea.rudolf.keenetic.link/` is currently running version **1.27.0**, which does NOT include the Projects REST API. Agentic workflows (kanban automation, CI integrations, MCP-style tooling) cannot programmatically move issues between Kanban columns on 1.27.0 — only drag-and-drop in the UI works. ## Why 1.27.0 is broken for Projects API - `https://github.com/go-gitea/gitea/issues/14299` ("API for projects") — closed via PR #38691 on **2026-08-08** (commit `7fae3d5db3df8996f39b2b4ce4435158c5c54b66`). - That PR added full REST API for project boards (repo, org, user scopes) — list, create, get, update, delete projects; list/create/get/update/delete columns; issue-to-column assignment, column moves, reorder. ~1500 lines of code + swagger. All behind the same token scopes as the rest of the API. - `routers/api/v1/shared/project.go` and `routers/api/v1/swagger/project.go` did not exist on 1.27.0 (verified via `git ls-tree v1.27.0 --name-only | grep project` → empty). - Current Gitea 1.27.0 instance at `gitea.rudolf.keenetic.link` ships **before** this commit. ## What landed and where | Tag | Date | Has Projects API? | |-----|------|--------------------| | v1.27.0 | 2026-07-13 | ❌ no | | v1.27.1 | 2026-07-27 | ❌ no | | v1.27.2 | 2026-08-13 | needs verification (5 days after #38691 merge, but no explicit projects file in shallow listing) | | v1.27.3 | 2026-08-29 | needs verification | | v1.28.0-dev | post-2026-08-29 | ✅ yes (commit `7fae3d5db` reachable in main) | | main | today | ✅ yes | The PR #38691 is currently reachable only on `main` and `v1.28.0-dev`. No release tag yet contains it. ## Reference issues and PRs - Upstream feature request: https://github.com/go-gitea/gitea/issues/14299 (closed via #38691) - Upstream kanban-for-agents request: https://github.com/go-gitea/gitea/issues/37151 - Merged PR (commit on main): https://github.com/go-gitea/gitea/commit/7fae3d5db3df8996f39b2b4ce4435158c5c54b66 - Closed PRs leading to this work: - https://github.com/go-gitea/gitea/pull/36784 — merged (multiple-projects-per-issue) - https://github.com/go-gitea/gitea/pull/36831 — closed (superseded by #37518 then #38691) - https://github.com/go-gitea/gitea/pull/37036 — closed (covered by #36784 + #38691) - https://github.com/go-gitea/gitea/pull/37518 — closed (superseded by #38691) - https://github.com/go-gitea/gitea/pull/38691 — merged 2026-08-08, fixes #14299 - Companion issue: https://github.com/go-gitea/gitea/issues/34969 (project migration API) - Companion issue: https://github.com/go-gitea/gitea/issues/20988 (import/export) - Companion issue: https://github.com/go-gitea/gitea/issues/19178 (activity feed for projects) ## Repro / current state 1. Create an Org1/Test1 issue (works via API). 2. `POST /api/v1/repos/Org1/Test1/issues` — works. 3. `PATCH /api/v1/repos/Org1/Test1/issues/{idx} {"projects": [4]}` — **works** (attach issue to project). 4. `POST /Org1/Test1/issues/{idx}/projects/column` — **404** (web route requires session cookie, basic auth is API-only — see `services/auth/basic.go:35`). 5. `POST /api/v1/orgs/Org1/projects/4/columns/{id}/cards` — **404 page not found** (the entire `routers/api/v1/org/projects.go` file does not exist in 1.27.0). 6. Drag-and-drop in UI works as expected. Currently issue `Org1/Test1#3` is bound to project `Org1/projects#4` (Proj1) but sits in the default column (Backlog, id=10) because the agent cannot move it via API. ## Plan 1. Upgrade the Gitea instance to a build containing `7fae3d5db` (either track `main` or build a release that ships the PR). 2. Verify with a minimal smoke test against `/api/v1/orgs/{org}/projects` — must return 200 with the existing `Proj1` payload. 3. Re-run the move test: `POST /api/v1/orgs/Org1/projects/4/columns/12/cards {"issue_id": 3}` — should now return 200/201. 4. Migrate any existing tracking workflows that depended on title-prefix status to use the new Projects API endpoints. 5. Close this issue. ## Risk Upgrading Gitea across a minor version (1.27 → 1.28) requires a database migration. The migration that ships with `7fae3d5db` adds a column to `project_board` — should be reviewed before applying. Snapshot the Gitea DB before upgrade. ## Related admin/brencher context - Self-hosted Gitea at `gitea.rudolf.keenetic.link` runs in stack `gitea` (`admin/gitea`). - brencher deploys compose files from `admin/ansible` repo via brencher bot (not via Gitea APIs). - The Gitea upgrade is performed out-of-band from brencher (Docker image swap + DB migration). --- 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Author
Contributor

First PR opened: admin/ansible#37 (bump 1.27.0 → 1.27.3).

This is step 1 of two: validates the upgrade path without schema changes. Step 2 (1.28.0 with Projects API) will be a follow-up once 1.28.x ships.

First PR opened: admin/ansible#37 (bump 1.27.0 → 1.27.3). This is step 1 of two: validates the upgrade path without schema changes. Step 2 (1.28.0 with Projects API) will be a follow-up once 1.28.x ships.
Author
Contributor

Release notes between 1.27.0 and current main

Compiled from upstream CHANGELOG.md and git log --grep="[security]".

Release timeline

Tag Date Notes
v1.27.0 2026-07-13 current prod
v1.27.1 2026-07-27 OAuth2 2FA + 27 bugfixes
v1.27.2 2026-08-14 7 SECURITY fixes + 18 bugfixes
v1.27.3 2026-08-29 18 SECURITY fixes + 19 bugfixes
v1.28.0-dev post 2026-08-29 ~3000+ commits since, includes #38691 Projects API

SECURITY-relevant fixes shipped AFTER 1.27.0 (per CHANGELOG.md)

1.27.3 (most relevant for step-1 PR):

  • fix(packages): restrict/limited/token-scope access (#39058) — 5 related PRs bundled together. Affects Alpine, Maven, Swift, OneDev, GitLab probes. Likely CVE-grade issues.
  • fix(attachments): enforce owning repository path (#39077) — path-traversal-like class
  • fix(markup): enforce same-repository issue access (#39054) — cross-repo info leak
  • fix(actions): verify raw artifact signatures first (#39053) — supply-chain integrity
  • fix(api): hide limited users from restricted viewers (#39039) — privacy
  • fix(repo): limit gitignore template selections (#39040)
  • fix(migrations): cancel GitLab version probes (#39035) — unbounded response DoS
  • fix(migrations): bound OneDev version responses (#39033) — unbounded response DoS
  • fix(packages): limit Swift package manifests (#39032)
  • fix(packages): limit Maven checksum uploads (#39031)
  • fix(packages): bound Alpine metadata entries (#39029)
  • fix(actions): enforce fork pull request trust boundaries (#39018)
  • fix(git): restrict hook permissions (#39016)
  • fix(api): enforce repository creation token authorization (#39014)
  • fix(api): enforce public-only scope for compare heads (#39013)
  • fix(repo): hide repositories of hidden owners (#39012)
  • fix: avoid enumerating every public repository in issue search (#39000)
  • refactor: private endpoints (#38965)

1.27.2 (additionally):

  • Fix: update collaborator access mode and httpsign (#38895)
  • Fix(actions): resolve pull_request_target reusable workflows at the base commit (#38897)
  • Fix(auth): set WebAuthn user verification per request (#38810)
  • Fix(deps): update dependency mermaid to v11.16.1 (#38816) — advisory
  • Fix: render highlight language (#38795)

1.27.1:

  • fix(oauth2): enforce mandatory 2FA policy on OAuth2 authorize/grant endpoints (#38606) — security-relevant

Security dependency bumps landed AFTER 1.27.3 (commits to main, not yet in any release)

From git log v1.27.3..FETCH_HEAD --grep="[security]":

  • 1b2479b548 fix(deps): update module golang.org/x/crypto to v0.56.0 [security] (#39219)
  • e223c42ee6 fix(deps): update module golang.org/x/mod to v0.40.0 [security] (#38914)
  • 133a3b8567 fix(deps): update module golang.org/x/image to v0.45.0 [security] (#38930)
  • b349a4e746 fix(deps): update dependency mermaid to v11.16.1 [security] (#38813)
  • 39cc4db4ba fix(deps): update module github.com/getkin/kin-openapi to v0.144.0 [security] (#38623)
  • be41cff5e2 fix(deps): update dependency js-yaml to v5.2.2 [security] (#38622)
  • bc3f63095b fix(deps): update module google.golang.org/grpc to v1.82.1 [security] (#38567)
  • b565f3e00a fix(deps): update module golang.org/x/image to v0.43.0 [security] (#38219)

Non-security notable changes

1.27.1 features/enhancements:

  • enhance: improve diff contrast in light and dark themes
  • fix(api): align Swagger schemas for UserSettings and TopicListResponse

1.27.2 enhancements:

  • enhance: add missing npm package metadata properties

1.27.3 enhancements:

  • enhance: add permalinks to pull request reviews

Risks / regressions to watch

  1. OAuth2 2FA enforcement (1.27.1) — any 2FA-bypass setups on our Gitea may break. hermes user has no 2FA, so no action needed.
  2. API swagger alignment (1.27.1) — response shapes may change for /users/{username}/settings and topic list. We use both via brencher / ansible scripts. Diff against current usage.
  3. Path-traversal-like fixes (1.27.3 attachments, packages probes) — defense-in-depth, no expected breakage, but watch 5xx in logs after deploy.
  4. PR #38691 (Projects API) ships only on main / v1.28.0-dev — NOT in 1.27.3. Step-1 PR #37 brings 1.27.3. Step 2 PR (future) will jump to 1.28.0+ to enable Projects API.

Recommendation

PR #37 is still the right first step. The 18 SECURITY fixes in 1.27.3 alone are worth the bump regardless of Projects API. Step 2 (1.28.0) will land Projects API plus whatever additional SECURITY commits land before 1.28.0 ships.

🤖 Generated with Claude Code

## Release notes between 1.27.0 and current main Compiled from upstream `CHANGELOG.md` and `git log --grep="[security]"`. ### Release timeline | Tag | Date | Notes | |-----|------|-------| | v1.27.0 | 2026-07-13 | **current prod** | | v1.27.1 | 2026-07-27 | OAuth2 2FA + 27 bugfixes | | v1.27.2 | 2026-08-14 | 7 SECURITY fixes + 18 bugfixes | | v1.27.3 | 2026-08-29 | **18 SECURITY fixes** + 19 bugfixes | | v1.28.0-dev | post 2026-08-29 | ~3000+ commits since, includes #38691 Projects API | ### SECURITY-relevant fixes shipped AFTER 1.27.0 (per CHANGELOG.md) **1.27.3** (most relevant for step-1 PR): - `fix(packages): restrict/limited/token-scope access` (#39058) — 5 related PRs bundled together. Affects Alpine, Maven, Swift, OneDev, GitLab probes. Likely **CVE-grade** issues. - `fix(attachments): enforce owning repository path` (#39077) — path-traversal-like class - `fix(markup): enforce same-repository issue access` (#39054) — cross-repo info leak - `fix(actions): verify raw artifact signatures first` (#39053) — supply-chain integrity - `fix(api): hide limited users from restricted viewers` (#39039) — privacy - `fix(repo): limit gitignore template selections` (#39040) - `fix(migrations): cancel GitLab version probes` (#39035) — unbounded response DoS - `fix(migrations): bound OneDev version responses` (#39033) — unbounded response DoS - `fix(packages): limit Swift package manifests` (#39032) - `fix(packages): limit Maven checksum uploads` (#39031) - `fix(packages): bound Alpine metadata entries` (#39029) - `fix(actions): enforce fork pull request trust boundaries` (#39018) - `fix(git): restrict hook permissions` (#39016) - `fix(api): enforce repository creation token authorization` (#39014) - `fix(api): enforce public-only scope for compare heads` (#39013) - `fix(repo): hide repositories of hidden owners` (#39012) - `fix: avoid enumerating every public repository in issue search` (#39000) - `refactor: private endpoints` (#38965) **1.27.2** (additionally): - `Fix: update collaborator access mode and httpsign` (#38895) - `Fix(actions): resolve pull_request_target reusable workflows at the base commit` (#38897) - `Fix(auth): set WebAuthn user verification per request` (#38810) - `Fix(deps): update dependency mermaid to v11.16.1` (#38816) — advisory - `Fix: render highlight language` (#38795) **1.27.1**: - `fix(oauth2): enforce mandatory 2FA policy on OAuth2 authorize/grant endpoints` (#38606) — security-relevant ### Security dependency bumps landed AFTER 1.27.3 (commits to main, not yet in any release) From `git log v1.27.3..FETCH_HEAD --grep="[security]"`: - `1b2479b548 fix(deps): update module golang.org/x/crypto to v0.56.0 [security]` (#39219) - `e223c42ee6 fix(deps): update module golang.org/x/mod to v0.40.0 [security]` (#38914) - `133a3b8567 fix(deps): update module golang.org/x/image to v0.45.0 [security]` (#38930) - `b349a4e746 fix(deps): update dependency mermaid to v11.16.1 [security]` (#38813) - `39cc4db4ba fix(deps): update module github.com/getkin/kin-openapi to v0.144.0 [security]` (#38623) - `be41cff5e2 fix(deps): update dependency js-yaml to v5.2.2 [security]` (#38622) - `bc3f63095b fix(deps): update module google.golang.org/grpc to v1.82.1 [security]` (#38567) - `b565f3e00a fix(deps): update module golang.org/x/image to v0.43.0 [security]` (#38219) ### Non-security notable changes **1.27.1 features/enhancements**: - `enhance: improve diff contrast in light and dark themes` - `fix(api): align Swagger schemas for UserSettings and TopicListResponse` **1.27.2 enhancements**: - `enhance: add missing npm package metadata properties` **1.27.3 enhancements**: - `enhance: add permalinks to pull request reviews` ### Risks / regressions to watch 1. **OAuth2 2FA enforcement** (1.27.1) — any 2FA-bypass setups on our Gitea may break. hermes user has no 2FA, so no action needed. 2. **API swagger alignment** (1.27.1) — response shapes may change for `/users/{username}/settings` and topic list. We use both via brencher / ansible scripts. Diff against current usage. 3. **Path-traversal-like fixes** (1.27.3 attachments, packages probes) — defense-in-depth, no expected breakage, but watch 5xx in logs after deploy. 4. **PR #38691 (Projects API)** ships only on `main` / `v1.28.0-dev` — NOT in 1.27.3. Step-1 PR #37 brings 1.27.3. Step 2 PR (future) will jump to 1.28.0+ to enable Projects API. ### Recommendation PR #37 is still the right first step. The 18 SECURITY fixes in 1.27.3 alone are worth the bump regardless of Projects API. Step 2 (1.28.0) will land Projects API plus whatever additional SECURITY commits land before 1.28.0 ships. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Author
Contributor

Разница между текущим продом (v1.27.0) и новой версией (v1.27.3)

Только то, что реально войдёт при апгрейде. v1.28.0-dev — это не релиз, а указатель на ветку разработки, который автоматически перемещается при каждом коммите в main. Тег создан 2026-06-29 и не использовался для production-апгрейда.

Что входит

Раздел Изменения
SECURITY (всего 26) 18 в 1.27.3 + 7 в 1.27.2 + 1 в 1.27.1
API breaking 0
API changes (non-breaking) 2 — Link header in ListForks, Swagger-выравнивание UserSettings/TopicListResponse
API new 0
FEATURES 0
ENHANCEMENTS 3
BUGFIXES 50+
DB migration минимальный (тот же путь, что 1.27.0 → 1.27.3 внутри patch-серии)

Детальный список

SECURITY (26 фиксов)

1.27.1 (1):

  • fix(oauth2): enforce mandatory 2FA policy on OAuth2 authorize/grant endpoints (#38606)

1.27.2 (7):

  • Fix: update collaborator access mode and httpsign (#38895)
  • Refactor: external render (#38898)
  • Fix(actions): resolve pull_request_target reusable workflows at the base commit (#38897)
  • Refactor: markup render (#38869)
  • Fix(deps): update dependency mermaid to v11.16.1 (#38816)
  • Fix(auth): set WebAuthn user verification per request (#38810)
  • Fix: render highlight language (#38795)

1.27.3 (18):

  • fix(packages): restrict/limited/token-scope access (#39058, 5 PRs bundled — Alpine/Maven/Swift/OneDev/GitLab probes)
  • fix(attachments): enforce owning repository path (#39077)
  • fix(markup): enforce same-repository issue access (#39054)
  • fix(actions): verify raw artifact signatures first (#39053)
  • fix(api): hide limited users from restricted viewers (#39039)
  • fix(repo): limit gitignore template selections (#39040)
  • fix(migrations): cancel GitLab version probes (#39035, DoS-class)
  • fix(packages): limit Swift package manifests (#39032)
  • fix(migrations): bound OneDev version responses (#39033, DoS-class)
  • fix(packages): limit Maven checksum uploads (#39031)
  • fix(packages): bound Alpine metadata entries (#39029)
  • fix(actions): enforce fork pull request trust boundaries (#39018)
  • fix(git): restrict hook permissions (#39016)
  • fix(api): enforce repository creation token authorization (#39014)
  • fix(api): enforce public-only scope for compare heads (#39013)
  • fix(repo): hide repositories of hidden owners (#39012)
  • fix: avoid enumerating every public repository in issue search (#39000)
  • refactor: private endpoints (#38965)

ENHANCEMENTS (3)

  • enhance: add permalinks to pull request reviews (#39036)
  • enhance: add missing npm package metadata properties (#38831)
  • enhance: improve diff contrast in light and dark themes (#38574)

API changes (non-breaking, 2)

  • feat(api): add Link header in ListForks (#38063)
  • fix(api): align Swagger schemas for UserSettings and TopicListResponse (#38592)

BUGFIXES (50+)

Полный список в CHANGELOG.md. Большинство — Actions/pipeline hardening, LFS, packages edge-cases. Ничего не помечено BREAKING.

Что НЕ входит (что приходит с 1.28.x)

  • Projects REST API (PR #38691, commit 7fae3d5db) — merged 2026-08-08, но в v1.27.3 ещё нет. Это в main / v1.28.0-dev. Подтверждено через git ls-tree v1.27.3 --name-only | grep routers/api/v1/.*project → empty.
  • DB schema changes для Projects API (новая колонка в project_board через migration v333).

Влияние на наш деплой

  1. brencher bot — мы используем POST /api/v1/repos/{}/issues, PATCH /api/v1/.../issues/{idx} с полем projects, POST /api/v1/.../labels. Все эти endpoints доступны в 1.27.3 без изменений. Шаблонные изменения в swagger (#38592) могут сдвинуть порядок полей, но не их типы — наш код парсит по имени поля.
  2. OAuth2 2FA enforcement (#38606) — у пользователя hermes нет 2FA, не затрагивает.
  3. Link header в ListForks (#38063) — не используем.
  4. PUBLIC_URL_DETECTION default auto — это уже в 1.27.0, не в 1.27.3. Можно не трогать, либо проверить app.ini.

Про префикс dev в v1.28.0-dev

  • Это dev-указатель, не релиз. Создан автоматически Giteabot 2026-06-29 и с тех пор не перемещался (последний коммит 6ae42ca9c от 2026-09-06 — это v1.27.3-rc0 подготовка).
  • Не путать с реальным релизом 1.28.0. Когда 1.28.0 будет выпущен (по SemVer — после 1.27.x), будет новый тег v1.28.0 без dev-суффикса.
  • Образ docker.gitea.com/gitea:1.28.0-dev существует на Docker Hub (Giteabot его регулярно собирает), но это pre-production-билд. Не использовать в production.
  • На Docker Hub могут быть теги 1.27, 1.27.3, 1.28.0-dev, latest, nightly. Рекомендация: 1.27.3.

Резюме

Метрика 1.27.0 → 1.27.3
Коммитов 1 (docs: fix the date in the changelog) — реальные изменения в коде не помечены отдельным коммитом между patch-релизами; они идут между 1.27.0→1.27.1→1.27.2→1.27.3 (1.27.2 = ~150 коммитов от 1.27.1, 1.27.3 = ~50 коммитов от 1.27.2).
SECURITY 26 фиксов
Breaking 0
New API endpoints 0
DB schema changes минимальные
Risk level Low (patch-release, внутри одной minor-серии)

PR #37 (bump 1.27.0 → 1.27.3) — корректный первый шаг. Step 2 (1.28.0 для Projects API) — отдельный будущий PR после выхода реального 1.28.0 stable.

🤖 Generated with Claude Code

## Разница между текущим продом (v1.27.0) и новой версией (v1.27.3) Только то, что реально войдёт при апгрейде. `v1.28.0-dev` — это **не релиз**, а указатель на ветку разработки, который автоматически перемещается при каждом коммите в main. Тег создан `2026-06-29` и не использовался для production-апгрейда. ### Что входит | Раздел | Изменения | |--------|-----------| | **SECURITY (всего 26)** | 18 в 1.27.3 + 7 в 1.27.2 + 1 в 1.27.1 | | **API breaking** | 0 | | **API changes (non-breaking)** | 2 — `Link header in ListForks`, Swagger-выравнивание `UserSettings`/`TopicListResponse` | | **API new** | 0 | | **FEATURES** | 0 | | **ENHANCEMENTS** | 3 | | **BUGFIXES** | 50+ | | **DB migration** | минимальный (тот же путь, что 1.27.0 → 1.27.3 внутри patch-серии) | ### Детальный список #### SECURITY (26 фиксов) **1.27.1** (1): - `fix(oauth2): enforce mandatory 2FA policy on OAuth2 authorize/grant endpoints` (#38606) **1.27.2** (7): - `Fix: update collaborator access mode and httpsign` (#38895) - `Refactor: external render` (#38898) - `Fix(actions): resolve pull_request_target reusable workflows at the base commit` (#38897) - `Refactor: markup render` (#38869) - `Fix(deps): update dependency mermaid to v11.16.1` (#38816) - `Fix(auth): set WebAuthn user verification per request` (#38810) - `Fix: render highlight language` (#38795) **1.27.3** (18): - `fix(packages): restrict/limited/token-scope access` (#39058, **5 PRs bundled** — Alpine/Maven/Swift/OneDev/GitLab probes) - `fix(attachments): enforce owning repository path` (#39077) - `fix(markup): enforce same-repository issue access` (#39054) - `fix(actions): verify raw artifact signatures first` (#39053) - `fix(api): hide limited users from restricted viewers` (#39039) - `fix(repo): limit gitignore template selections` (#39040) - `fix(migrations): cancel GitLab version probes` (#39035, DoS-class) - `fix(packages): limit Swift package manifests` (#39032) - `fix(migrations): bound OneDev version responses` (#39033, DoS-class) - `fix(packages): limit Maven checksum uploads` (#39031) - `fix(packages): bound Alpine metadata entries` (#39029) - `fix(actions): enforce fork pull request trust boundaries` (#39018) - `fix(git): restrict hook permissions` (#39016) - `fix(api): enforce repository creation token authorization` (#39014) - `fix(api): enforce public-only scope for compare heads` (#39013) - `fix(repo): hide repositories of hidden owners` (#39012) - `fix: avoid enumerating every public repository in issue search` (#39000) - `refactor: private endpoints` (#38965) #### ENHANCEMENTS (3) - `enhance: add permalinks to pull request reviews` (#39036) - `enhance: add missing npm package metadata properties` (#38831) - `enhance: improve diff contrast in light and dark themes` (#38574) #### API changes (non-breaking, 2) - `feat(api): add Link header in ListForks` (#38063) - `fix(api): align Swagger schemas for UserSettings and TopicListResponse` (#38592) #### BUGFIXES (50+) Полный список в CHANGELOG.md. Большинство — Actions/pipeline hardening, LFS, packages edge-cases. Ничего не помечено BREAKING. ### Что НЕ входит (что приходит с 1.28.x) - **Projects REST API** (PR #38691, commit `7fae3d5db`) — merged 2026-08-08, но в `v1.27.3` ещё нет. Это в `main` / `v1.28.0-dev`. Подтверждено через `git ls-tree v1.27.3 --name-only | grep routers/api/v1/.*project` → empty. - **DB schema changes** для Projects API (новая колонка в `project_board` через migration `v333`). ### Влияние на наш деплой 1. **brencher bot** — мы используем `POST /api/v1/repos/{}/issues`, `PATCH /api/v1/.../issues/{idx}` с полем `projects`, `POST /api/v1/.../labels`. Все эти endpoints доступны в 1.27.3 без изменений. Шаблонные изменения в swagger (#38592) могут сдвинуть порядок полей, но не их типы — наш код парсит по имени поля. 2. **OAuth2 2FA enforcement** (#38606) — у пользователя `hermes` нет 2FA, **не затрагивает**. 3. **Link header в ListForks** (#38063) — не используем. 4. **`PUBLIC_URL_DETECTION` default `auto`** — это **уже в 1.27.0**, не в 1.27.3. Можно не трогать, либо проверить `app.ini`. ### Про префикс dev в v1.28.0-dev - Это **dev-указатель**, не релиз. Создан автоматически Giteabot 2026-06-29 и с тех пор **не перемещался** (последний коммит `6ae42ca9c` от 2026-09-06 — это `v1.27.3-rc0` подготовка). - **Не путать с реальным релизом** `1.28.0`. Когда 1.28.0 будет выпущен (по SemVer — после 1.27.x), будет новый тег `v1.28.0` без `dev`-суффикса. - Образ `docker.gitea.com/gitea:1.28.0-dev` **существует на Docker Hub** (Giteabot его регулярно собирает), но это pre-production-билд. **Не использовать в production.** - На Docker Hub могут быть теги `1.27`, `1.27.3`, `1.28.0-dev`, `latest`, `nightly`. Рекомендация: `1.27.3`. ### Резюме | Метрика | 1.27.0 → 1.27.3 | |---------|----------------| | Коммитов | 1 (docs: fix the date in the changelog) — реальные изменения в коде не помечены отдельным коммитом между patch-релизами; они идут между 1.27.0→1.27.1→1.27.2→1.27.3 (1.27.2 = ~150 коммитов от 1.27.1, 1.27.3 = ~50 коммитов от 1.27.2). | | SECURITY | 26 фиксов | | Breaking | 0 | | New API endpoints | 0 | | DB schema changes | минимальные | | Risk level | **Low** (patch-release, внутри одной minor-серии) | PR #37 (bump 1.27.0 → 1.27.3) — корректный первый шаг. Step 2 (1.28.0 для Projects API) — отдельный будущий PR после выхода реального 1.28.0 stable. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/brencher#63