Codeberg Will Switch Off Pages v2 on Dec. 31, While Its Own Migration Guide Still Says Indefinitely

Codeberg will stop serving every site still on Pages v2 on Dec. 31, 2026, according to a post from the non-profit that runs the Forgejo host. Its own migration guide, read on Oct. 17, says the opposite.

Andreas Shimokawa of Codeberg e.V. published the notice on Oct. 7. It says v2 "will be shut off completely on 2026-12-31" and singles out users who "never set up a webhook in their repository". It gives no count of affected sites, saying only that "A lot of users already migrated."

Two Codeberg pages, two answers

The migration guide says the new git-pages service has existed "Since December 2025" and that the old v2 deployment "will continue working indefinitely". It lists no deadlines.

The blog post is dated, signed and specific. The guide text fetched carries no date. The Terminal cannot tell from the pages which is current, so a site owner should plan for Dec. 31 and treat the guide's "indefinitely" as unconfirmed until Codeberg edits it.

What breaks when you move

Codeberg says migration needs no downtime: once you use a new deployment method, git-pages serves the site. To check which server answers, read the Server header. pages-server means v2 and git-pages means the new one. The post also links a check tool at codeberg.page/migration-check/.

The guide lists the breaking changes:

Change	What to do
raw.codeberg.page removed	Serve from your page; CORS headers are now set
path no longer redirects to path.html	Add a redirect rule for each page
A repo named pages no longer falls back to its default branch	Use a branch named pages
/repository/@branch access removed	Arbitrary repo and branch serving is restricted

Splat redirects survive only in simple forms such as /old-path/* /new-path/:splat. A pattern like /* /:splat.html, the usual workaround for the missing html mapping, is not supported.

Two routes off v2

Sites with a hand-uploaded pages branch need a Forgejo webhook with the target https://username.codeberg.page/repository-name/ and a branch filter of pages. If both the repository and the branch are named pages, the target is https://username.codeberg.page/.

Sites built by CI replace their push step with the official git-pages Forgejo Action. Content is no longer fetched automatically, so something must tell git-pages when it changes. That explains the blog's focus on people without a webhook: their sites never notified anything.

Codeberg runs on Forgejo, and Forgejo 17.0, released Oct. 15, includes a webhook change that the Terminal reported needs manual migration. Neither Codeberg page says whether that change touches the Pages webhook.

What the pages do not cover

Custom domains are the gap. The guide says git-pages supports them and points to an updated setup guide for replacing old DNS records, but gives no steps itself, and the blog does not mention DNS. A site on its own domain should read that guide before changing records, since the guide is the one Codeberg page already in doubt.

Shimokawa's notice names no grace period after Dec. 31. Source hosting is being reworked elsewhere too: Anthropic replaced Git with Scion after merges hit 30,401 in a day.

Codeberg has not said whether it will correct the migration guide. Until it does, the Server header on a site's own address is the only test that settles which server is answering.