Forgejo Migration Check — Gitea 1.22 cutoff

It reads the image lines of a docker-compose or compose.yaml file and flags what breaks a Gitea to Forgejo switch: a Gitea tag past 1.22, a first hop that is not Forgejo v10.0.x, Forgejo majors past end of life on the Forgejo release schedule, unpinned tags, Gitea's act_runner and custom GPL builds. Each finding has a line number and the fix.

Self-hosting admins, homelab owners and DevOps teams that run Gitea with Docker or Podman compose and plan the move to Forgejo, plus agencies that maintain several client Git servers. It suits anyone who must know, before pulling a new image, whether the Gitea data can go to Forgejo without manual database edits.

The Forgejo upgrade guide and release schedule are free and correct, but they do not read your compose file. Docker will pull forgejo:11 onto a Gitea data volume without a warning, and a floating gitea:latest tag moves past 1.22 on the next pull. The check compares every image line with those published rules and dates.

Free: the VS Code extension and the web page check any compose file with all eight rules and show every finding with its fix, no key needed. Paid, $29 once for one licence key per person or team seat: export a dated two-hop migration report in Markdown and JSON for the change ticket, one file per compose file in the workspace.

Gitea Enterprise, the vendor's paid support plan, lists $19 per user per month, or $9.50 per user per month with a one-year commitment, on about.gitea.com/pricing. Staying on Gitea is a valid choice; this check is for teams that have decided to move to Forgejo and want the upgrade path verified line by line before the switch.