Forgejo 17.0 expands self-hosted CI — but existing Actions webhooks need manual migration

On October 15, 2026, Forgejo released version 17.0 of its community-developed, self-hosted Git collaboration platform. The release adds richer Forgejo Actions APIs for rerunning completed workflows and jobs, querying individual step logs and job metadata, and rendering Markdown job summaries with Forgejo Runner 13.2 or newer. It improves Git LFS file navigation and pointer inspection, supports migration of repositories and review discussions from Bitbucket Data Center, and adds optional invitation-based organization membership. Crucially, the older Actions 'action run' webhook events are deprecated in favour of workflow-run events with different headers and payload fields, and existing webhook subscriptions cannot be migrated automatically.

Teams choosing a self-hosted Git forge often rely on webhooks and Actions to connect CI, chat, deployment and incident workflows. Forgejo 17.0 closes practical automation gaps relative to hosted platforms, but its new workflow event contract can break webhook receivers that assume the old headers or completion timing. The upgrade also changes how absolute links in rendered repository documents resolve, which can alter existing documentation links. These are concrete migration decisions for small self-hosted teams rather than merely a cosmetic major-version release.

Forgejo 17.0 introduces API endpoints to rerun entire completed workflow runs or individual completed jobs, retrieve a specific job's details and filter logs by substring or step. Logs can be returned as NDJSON. Forgejo Runner 13.2 or later can produce job summaries through $FORGEJO_STEP_SUMMARY; $GITHUB_STEP_SUMMARY is accepted for GitHub Actions compatibility. The summaries appear above logs and support tables, Mermaid diagrams and KaTeX. These capabilities reduce the need for custom log scraping and make test output easier to interpret without leaving the forge.

The 'action run' webhook event is deprecated in favour of 'workflow run' events. New event headers, including X-*-Event and X-*-Event-Type, and the action field differ. The platform cannot automatically migrate existing subscriptions, because downstream receivers may depend on those exact values. Operators should inventory consumers, add handling for workflow-run events, and validate event statuses and payloads before removing old hooks. Completion notifications for workflow runs arrive only after all jobs have terminated; separate job-status events can report intermediate states.

In rendered repository documents, absolute resource links now resolve from the repository root instead of the instance root. Issue and pull-request comments retain instance-root behaviour. That difference improves compatibility with other forges but may change links in existing README files or docs. The release also adds better Git LFS navigation, pointer-file views and ways to find commits referencing a stored LFS object. Operators should test internal docs and LFS cleanup workflows during upgrade.

Forgejo can now import from Bitbucket Data Center, including pull requests, reviews, comments and discussion threads; this path requires an HTTP access token and HTTPS SCM Hosting. Organization administrators can opt into invitation-based membership through [service].ADD_MEMBERS_BY_INVITATIONS = true; invitations expire after 14 days by default, while authentication providers can still add members directly. FUNDING.yml can show donation options in repository and profile views.

Forgejo 17.0 is a non-LTS release supported until January 28, 2027. Operators prioritising maintenance duration can remain on Forgejo 15.0 LTS, supported until July 15, 2027. The project recommends backups and careful review of breaking changes before upgrades; replacing the binary or image is straightforward, but that does not eliminate integration compatibility testing.