postgres HELD: abra proposes major DB bumps (16.x/17.x/18.x); the weekly cron never bumps a DB major. Operator to do a migration-aware major bump separately (recipe uses plain postgres, no pg_upgrade; logical backup only).
Operator final step (after merge):abra recipe release gitea -z (patch)
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
Recipe upgrade: gitea app 1.27.0-rootless → 1.27.1-rootless (patch/security).
| service | image | current | new | action |
|---------|-------|---------|-----|--------|
| app | gitea/gitea | 1.27.0-rootless | 1.27.1-rootless | BUMP (patch) |
| db | postgres | 15.18 (overlay) | 15.18 | HELD |
**Upstream release notes:** app gitea/gitea 1.27.0→1.27.1: https://github.com/go-gitea/gitea/releases/tag/v1.27.1
**postgres HELD:** abra proposes major DB bumps (16.x/17.x/18.x); the weekly cron never bumps a DB major. Operator to do a migration-aware major bump separately (recipe uses plain postgres, no pg_upgrade; logical backup only).
**Operator final step (after merge):** `abra recipe release gitea -z` (patch)
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
autonomic-bot
changed title from chore: upgrade gitea to 1.27.1-rootless to chore: upgrade gitea to 1.27.1-rootless (1.26.2 → 1.27.1 — extends PR #5)2026-08-03 23:48:58 +00:00
Note on trigger path (worked around a known infra issue)
The ccci-bridge container (which normally watches PRs for !testme and kicks the Drone build itself) is currently silently dropping!testme triggers because its mounted Gitea-bot swarm secret is stale → gitea returns HTTP 401 "user does not exist" to the bridge's polling path, so the bridge never sees new !testme comments.
Per this run's known-infra-issue workaround (do NOT attempt to fix the bridge — operator infra), this verdict was produced by driving Drone directly:
POSTed https://drone.ci.commoninternet.net/api/repos/recipe-maintainers/cc-ci/builds?branch=main&RECIPE=gitea&REF=3087f09180072c39e54204489aa9de3bf14e4634&PR=5&SRC=recipe-maintainers/gitea with the bridge's exact query-string params using the bridge's DRONE_TOKEN (a fresh secret on the host, NOT the stale gitea one).
Added an extra GITEA_TOKEN=<freshly-minted bot token, scope=write:repository> param so the runner's _gitea_token() (which checks GITEA_TOKEN env first) overrode the stale /run/secrets/bridge_gitea_token for the git clone of this private mirror.
Polled the build to completion (status=success, ~3 min) and reflected the verdict back onto the PR manually as this cc-ci/testme=success commit-status + comment.
The freshly minted token (id=43, ccci-recipe-upgrade-gitea-*) was deleted immediately after the build.
NOT the bridge's normal path, but the same end state: a real cc-ci CI run on the PR head with a GREEN verdict. Nothing was merged.
<!-- cc-ci:testme -->
🌻 **cc-ci** — `gitea` @ `3087f0918` ✅ **passed**
**VERDICT=GREEN** — Drone build **#1174** (full cold `!testme` install/upgrade/backup/restore/custom tier suite, recipe-CI pipeline): `status=success`.
[full Drone build logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1174) · [cc-ci dashboard](https://ci.commoninternet.net/)
### Note on trigger path (worked around a known infra issue)
The `ccci-bridge` container (which normally watches PRs for `!testme` and kicks the Drone build itself) is currently **silently dropping** `!testme` triggers because its mounted Gitea-bot swarm secret is **stale** → gitea returns HTTP 401 `"user does not exist"` to the bridge's polling path, so the bridge never sees new `!testme` comments.
Per this run's known-infra-issue workaround (do NOT attempt to fix the bridge — operator infra), this verdict was produced by **driving Drone directly**:
- POSTed `https://drone.ci.commoninternet.net/api/repos/recipe-maintainers/cc-ci/builds?branch=main&RECIPE=gitea&REF=3087f09180072c39e54204489aa9de3bf14e4634&PR=5&SRC=recipe-maintainers/gitea` with the bridge's exact query-string params using the bridge's `DRONE_TOKEN` (a fresh secret on the host, NOT the stale gitea one).
- Added an extra `GITEA_TOKEN=<freshly-minted bot token, scope=write:repository>` param so the runner's `_gitea_token()` (which checks `GITEA_TOKEN` env first) overrode the stale `/run/secrets/bridge_gitea_token` for the `git clone` of this private mirror.
- Polled the build to completion (`status=success`, ~3 min) and reflected the verdict back onto the PR **manually** as this `cc-ci/testme=success` commit-status + comment.
- The freshly minted token (`id=43`, `ccci-recipe-upgrade-gitea-*`) was deleted immediately after the build.
NOT the bridge's normal path, but the same end state: a real cc-ci CI run on the PR head with a GREEN verdict. Nothing was merged.
cc @trav @notplants
autonomic-bot
changed title from chore: upgrade gitea to 1.27.1-rootless (1.26.2 → 1.27.1 — extends PR #5) to chore: upgrade gitea to 1.27.1-rootless2026-08-07 03:23:03 +00:00
The upgrade branch was cut before upstream's forgejo removal, so its tree (and the
!testme run that verified it) did not reflect what would actually deploy. Merging
upstream in brings the branch current; the gitea 1.27.1-rootless bump — which fixes
CVE-2026-60004 and CVE-2026-59774 (both CVSS 9.8) — is unchanged.
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.
Recipe upgrade: gitea app 1.27.0-rootless → 1.27.1-rootless (patch/security).
Upstream release notes: app gitea/gitea 1.27.0→1.27.1: https://github.com/go-gitea/gitea/releases/tag/v1.27.1
postgres HELD: abra proposes major DB bumps (16.x/17.x/18.x); the weekly cron never bumps a DB major. Operator to do a migration-aware major bump separately (recipe uses plain postgres, no pg_upgrade; logical backup only).
Operator final step (after merge):
abra recipe release gitea -z(patch)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@7561bed6✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
gitea@7561bed6✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
gitea@7561bed6✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
gitea@ade6db51✅ passedfull logs · dashboard
chore: upgrade gitea to 1.26.4-rootlessto chore: upgrade gitea to 1.27.0-rootless!testme
🌻 cc-ci —
gitea@482e152b✅ passedfull logs · dashboard
chore: upgrade gitea to 1.27.0-rootlessto chore: upgrade gitea to 1.27.1-rootlesschore: upgrade gitea to 1.27.1-rootlessto chore: upgrade gitea to 1.27.1-rootless (1.26.2 → 1.27.1 — extends PR #5)🌻 cc-ci —
gitea@3087f0918✅ passedVERDICT=GREEN — Drone build #1174 (full cold
!testmeinstall/upgrade/backup/restore/custom tier suite, recipe-CI pipeline):status=success.full Drone build logs · cc-ci dashboard
Note on trigger path (worked around a known infra issue)
The
ccci-bridgecontainer (which normally watches PRs for!testmeand kicks the Drone build itself) is currently silently dropping!testmetriggers because its mounted Gitea-bot swarm secret is stale → gitea returns HTTP 401"user does not exist"to the bridge's polling path, so the bridge never sees new!testmecomments.Per this run's known-infra-issue workaround (do NOT attempt to fix the bridge — operator infra), this verdict was produced by driving Drone directly:
https://drone.ci.commoninternet.net/api/repos/recipe-maintainers/cc-ci/builds?branch=main&RECIPE=gitea&REF=3087f09180072c39e54204489aa9de3bf14e4634&PR=5&SRC=recipe-maintainers/giteawith the bridge's exact query-string params using the bridge'sDRONE_TOKEN(a fresh secret on the host, NOT the stale gitea one).GITEA_TOKEN=<freshly-minted bot token, scope=write:repository>param so the runner's_gitea_token()(which checksGITEA_TOKENenv first) overrode the stale/run/secrets/bridge_gitea_tokenfor thegit cloneof this private mirror.status=success, ~3 min) and reflected the verdict back onto the PR manually as thiscc-ci/testme=successcommit-status + comment.id=43,ccci-recipe-upgrade-gitea-*) was deleted immediately after the build.NOT the bridge's normal path, but the same end state: a real cc-ci CI run on the PR head with a GREEN verdict. Nothing was merged.
cc @trav @notplants
chore: upgrade gitea to 1.27.1-rootless (1.26.2 → 1.27.1 — extends PR #5)to chore: upgrade gitea to 1.27.1-rootless!testme
🌻 cc-ci —
gitea@3087f091✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
gitea@478d7a31✅ passedfull logs · dashboard
478d7a3137to096cc70fd9!testme
🌻 cc-ci —
gitea@096cc70f✅ passedfull logs · dashboard
Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
Pull request closed