For a patch series, this is a large security batch (fork-PR Actions approval bypasses → code
execution on self-hosted runners; restricted-user data leaks across API/packages/activity; package
registry upload DoS amplification; token-scope enforcement; Git hook permission regression). Full
CVE list is published on the vendor blog (NOT on GitHub):
Verbatim advisory scan: see the upgrade log cc-ci-logs/upgrades/gitea-upgrade-2026-08-31.md — 24
CVEs counted deterministically + 1 adjudicated FIXED (CVE-2026-62925) + 1 named only in the vendor
blog (CVE-2026-70406) = 26. (CVE-2025-68939 = STILL-UNKNOWN, not counted.)
Operator action required
No breaking changes / no migrations / no config changes — pure patch bump.
Postgres left at 15.19: the 16/17/18 majors are held per the standing note (plain postgres;
operator dump/restore when the major is bumped). Do NOT bump the DB major here.
Recommended release command (runs the semver bump + tag + publish after this PR merges):
abra recipe release gitea -z
Notes
Direct deploy verified on cc-ci (dev-gitea, --chaos, then torn down): app converged, healthcheck
and /api/v1/version return 200, version endpoint reports 1.27.3.
The read-only app.ini warning observed at deploy is the known condition covered by PR #4
(fix-app-ini-writable) — this upgrade does NOT touch it.
PR #4 (fix-app-ini-writable) was left untouched by this upgrade.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
# chore: upgrade to 1.27.3-rootless
Upgrade the gitea app image `1.27.2-rootless` → `1.27.3-rootless`.
## Image tags
| service | image | current → new |
|---------|-------|---------------|
| app | gitea/gitea | `1.27.2-rootless` → `1.27.3-rootless` |
| db | postgres | `15.19` (unchanged — major held) |
**Upstream release notes:**
- app gitea/gitea 1.27.2→1.27.3: https://github.com/go-gitea/gitea/releases/tag/v1.27.3
## Security — 26 CVEs fixed (strongly recommended upgrade)
For a patch series, this is a **large security batch** (fork-PR Actions approval bypasses → code
execution on self-hosted runners; restricted-user data leaks across API/packages/activity; package
registry upload DoS amplification; token-scope enforcement; Git hook permission regression). Full
CVE list is published on the vendor blog (NOT on GitHub):
https://blog.gitea.com/release-of-1.27.3/
Verbatim advisory scan: see the upgrade log `cc-ci-logs/upgrades/gitea-upgrade-2026-08-31.md` — 24
CVEs counted deterministically + 1 adjudicated FIXED (CVE-2026-62925) + 1 named only in the vendor
blog (CVE-2026-70406) = **26**. (CVE-2025-68939 = STILL-UNKNOWN, not counted.)
## Operator action required
- **No breaking changes / no migrations / no config changes** — pure patch bump.
- **Postgres left at 15.19**: the `16/17/18` majors are held per the standing note (plain postgres;
operator dump/restore when the major is bumped). Do NOT bump the DB major here.
- Recommended release command (runs the semver bump + tag + publish after this PR merges):
```
abra recipe release gitea -z
```
## Notes
- Direct deploy verified on cc-ci (`dev-gitea`, `--chaos`, then torn down): app converged, healthcheck
and `/api/v1/version` return 200, version endpoint reports `1.27.3`.
- The read-only `app.ini` warning observed at deploy is the known condition covered by PR #4
(`fix-app-ini-writable`) — this upgrade does NOT touch it.
- PR #4 (`fix-app-ini-writable`) was left untouched by this upgrade.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
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.
chore: upgrade to 1.27.3-rootless
Upgrade the gitea app image
1.27.2-rootless→1.27.3-rootless.Image tags
1.27.2-rootless→1.27.3-rootless15.19(unchanged — major held)Upstream release notes:
Security — 26 CVEs fixed (strongly recommended upgrade)
For a patch series, this is a large security batch (fork-PR Actions approval bypasses → code
execution on self-hosted runners; restricted-user data leaks across API/packages/activity; package
registry upload DoS amplification; token-scope enforcement; Git hook permission regression). Full
CVE list is published on the vendor blog (NOT on GitHub):
https://blog.gitea.com/release-of-1.27.3/
Verbatim advisory scan: see the upgrade log
cc-ci-logs/upgrades/gitea-upgrade-2026-08-31.md— 24CVEs counted deterministically + 1 adjudicated FIXED (CVE-2026-62925) + 1 named only in the vendor
blog (CVE-2026-70406) = 26. (CVE-2025-68939 = STILL-UNKNOWN, not counted.)
Operator action required
16/17/18majors are held per the standing note (plain postgres;operator dump/restore when the major is bumped). Do NOT bump the DB major here.
Notes
dev-gitea,--chaos, then torn down): app converged, healthcheckand
/api/v1/versionreturn 200, version endpoint reports1.27.3.app.iniwarning observed at deploy is the known condition covered by PR #4(
fix-app-ini-writable) — this upgrade does NOT touch it.fix-app-ini-writable) was left untouched by this upgrade.Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
gitea@dd017ef4✅ passed → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1306(summary card unavailable — see the run for details.) full logs · dashboard
Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
Pull request closed