feat(forgejo): v16 pre-flight — reverse-proxy trust + image pin (#73) #74
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra!74
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "forgejo-v16-upgrade"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
Pre-flight config for the v16 upgrade (#73), per the verified upgrade plan:
[security] REVERSE_PROXY_TRUSTED_PROXIES = 10.89.0.0/24(the inspectedgitborgpodman bridge subnet) +REVERSE_PROXY_LIMIT = 1. v16 removed the*default — without this every request would appear to originate from Caddy (broken client IPs in audit logs / rate limiting).forgejo_image_tag: 15.0.4 → 16.0.0(exact released tag, 2026-07-16) + stale:15comment refs invault.example.yml.Runner v12.12.0 is confirmed compatible (v16 vendors exactly that module version). Apply happens in a maintenance window (backup → flush-queues → apply → doctor → verify); rollback is restore-from-backup — the schema migration is irreversible-forward.
Closes #73 is intentionally NOT used — the issue stays open until post-upgrade verification passes.
forgejo v16 pre-flight: reverse-proxy trust + image pin (#73)till feat(forgejo): v16 pre-flight — reverse-proxy trust + image pin (#73)