[Version-Watchdog-Failure] Forgejo or its runner is behind its own release line #923

New issue

Open

opened 2026-10-19 06:47:55 +00:00 by ci-reporter · 0 comments

ci-reporter commented

2026-10-19 06:47:55 +00:00

Member

Red check: not readable — the reporter names no red step. The output is below; the full log is in the Forgejo run.

The weekly version watchdog found the running Forgejo or its runner behind its own release line.

Forgejo runs 15.0.9, its own line has 15.0.10 (published 2026-10-12) — 1 fix release(s) behind. Release: https://codeberg.org/forgejo/forgejo/releases/tag/v15.0.10

What to do: raise the version as card 0.99 in 0 App Module.md describes (runner image, compose tag, validate before a runner major), read the release notes of every skipped release first, and write the new version into the version line of Operations/Server.md.

Not a finding: a new Forgejo major while ours is still maintained. The rules are in .forgejo/scripts/version-watchdog.py (card 0.100).

Run: http://forgejo:3000/Aregoland/aregoland/actions/runs/11082

**Red check:** not readable — the reporter names no red step. The output is below; the full log is in the Forgejo run. The weekly version watchdog found the running Forgejo or its runner behind its own release line. * **Forgejo** runs `15.0.9`, its own line has `15.0.10` (published 2026-10-12) — 1 fix release(s) behind. Release: https://codeberg.org/forgejo/forgejo/releases/tag/v15.0.10 **What to do:** raise the version as card 0.99 in `0 App Module.md` describes (runner image, compose tag, `validate` before a runner major), read the release notes of every skipped release first, and write the new version into the version line of `Operations/Server.md`. Not a finding: a new Forgejo major while ours is still maintained. The rules are in `.forgejo/scripts/version-watchdog.py` (card 0.100). Run: http://forgejo:3000/Aregoland/aregoland/actions/runs/11082