Compare commits

..
Author SHA1 Message Date
autonomic-bot 478d7a3137 chore: merge upstream main (BREAKING CHANGE: remove forgejo) into upgrade branch
cc-ci/testme cc-ci: success
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.
2026-08-10 16:24:51 +00:00
autonomic-bot 3087f09180 chore: upgrade gitea to 1.27.1-rootless
cc-ci/testme cc-ci: success
2026-08-03 23:48:26 +00:00
autonomic-bot 482e152b23 chore: upgrade gitea to 1.27.0-rootless
cc-ci/testme cc-ci: success
2026-07-24 04:07:59 +00:00
autonomic-bot ade6db5133 chore: upgrade gitea to 1.26.4-rootless
cc-ci/testme cc-ci: success
2026-07-13 20:12:13 +00:00
autonomic-bot 7561bed6e1 chore: upgrade gitea to 1.26.4-rootless
cc-ci/testme cc-ci: success
2026-06-22 21:20:16 +00:00
4 changed files with 4 additions and 12 deletions
+2 -2
View File
@@ -1,5 +1,5 @@
export APP_INI_VERSION=v23 export APP_INI_VERSION=v22
export DOCKER_SETUP_SH_VERSION=v3 export DOCKER_SETUP_SH_VERSION=v1
export PG_BACKUP_VERSION=v1 export PG_BACKUP_VERSION=v1
abra_backup_app() { abra_backup_app() {
+2 -2
View File
@@ -6,7 +6,7 @@ services:
image: "gitea/gitea:1.27.1-rootless" image: "gitea/gitea:1.27.1-rootless"
configs: configs:
- source: app_ini - source: app_ini
target: /etc/gitea/app.ini.init target: /etc/gitea/app.ini
- source: docker_setup_sh - source: docker_setup_sh
target: /usr/local/bin/docker-setup.sh target: /usr/local/bin/docker-setup.sh
mode: 0555 mode: 0555
@@ -87,7 +87,7 @@ services:
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}" - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolmaxage=100" - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolmaxage=100"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true" - "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true"
- coop-cloud.${STACK_NAME}.version=3.6.3+1.27.1-rootless - coop-cloud.${STACK_NAME}.version=3.6.0+1.24.2-rootless
networks: networks:
-8
View File
@@ -13,11 +13,3 @@ mkdir -p ${GITEA_CUSTOM} && chmod 0500 ${GITEA_CUSTOM}
# Prepare temp folder # Prepare temp folder
mkdir -p ${GITEA_TEMP} && chmod 0700 ${GITEA_TEMP} mkdir -p ${GITEA_TEMP} && chmod 0700 ${GITEA_TEMP}
if [ ! -w ${GITEA_TEMP} ]; then echo "${GITEA_TEMP} is not writable"; exit 1; fi if [ ! -w ${GITEA_TEMP} ]; then echo "${GITEA_TEMP} is not writable"; exit 1; fi
# Gitea 1.24+ writes settings back to app.ini on boot (e.g. WORK_PATH), which fails when app.ini is
# mounted directly as a read-only swarm config. So mount the rendered config as app.ini.init and seed
# a writable copy. Use `! -s` (empty), not `! -f`: old direct-mount upgrades leave a 0-byte app.ini.
if [ ! -s /etc/gitea/app.ini ]; then
cp /etc/gitea/app.ini.init /etc/gitea/app.ini
fi
chmod 0600 /etc/gitea/app.ini 2>/dev/null || true