# Forgejo 17.0 expands self-hosted CI — but existing Actions webhooks need manual migration Forgejo 17.0 adds workflow reruns, job summaries, better LFS inspection and Bitbucket Data Center migration. Operators must check breaking repository-link behaviour and replace deprecated Actions run webhooks manually. The October 15 Forgejo 17.0 release strengthens self-hosted Git and CI workflows, but webhook receivers need a migration because the new workflow-run events change headers and payload semantics. The release is non-LTS. - Status: Active - Published: 2026-10-16T17:24:39+13:00 - Updated: 2026-10-16T17:24:39+13:00 - Categories: Web Development, Cloud & Infrastructure, Deployment & DevOps, Developer Tools - Tags: CI/CD, Forgejo, Git LFS, open source, self-hosting, webhooks - Canonical HTML: https://beyondthe.news/dossiers/forgejo-17-actions-workflow-webhooks-ci-job-api-lfs-bitbucket-migration ## What changed 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. ## Why it matters 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. ## Actions gains job-level observability and control 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. ## Webhook migration is not automatic 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. ## Repository links and LFS workflows change 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. ## Migrations and membership administration get more practical 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. ## 17.0 is not the long-support track 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. ## Key details - Forgejo 17.0.0 released October 15, 2026; non-LTS end of support January 28, 2027. - Old 'action run' webhooks are deprecated; replacement workflow-run events use different headers and action payloads and require manual receiver migration. - Workflow completion notifications are sent after all jobs terminate; separate job-status webhooks expose intermediate transitions. - New API operations rerun completed workflows or jobs, query job details and filter logs by step or substring with NDJSON support. - Forgejo Runner 13.2+ supports Markdown job summaries using $FORGEJO_STEP_SUMMARY or compatible $GITHUB_STEP_SUMMARY. - Rendered repository document absolute links now resolve against the repository root; issue and PR comments do not change. - Git LFS management now includes pointer views and commit references. - Bitbucket Data Center migration supports repositories, pull requests, reviews, comments and threads. - Forgejo 15.0 LTS support continues until July 15, 2027. ## Builder takeaways - Inventory Forgejo Actions webhooks before upgrading and migrate receiving services to the workflow-run and job-status event contracts; test headers and completion semantics. - Use Runner 13.2+ if you want job summaries; write to $FORGEJO_STEP_SUMMARY to publish CI results directly in the forge. - Check absolute links in README files and rendered docs after upgrading because repository-root resolution differs from previous versions. - Test LFS pointer and retention workflows and confirm that external Bitbucket Data Center migration permissions are correctly scoped. - Choose the 15.0 LTS branch if support duration matters more than the new 17.0 features; back up the instance and secrets before a major upgrade. ## What to watch - Removal date for deprecated action-run webhooks and availability of migration tooling. - Follow-up 17.0.x fixes for workflow event and job rerun compatibility. - Whether job-summary and log APIs gain wider runner and client compatibility. - Next LTS Forgejo 19.0 planned for April 2027. ## Uncertainties - 17.0 is newly released; long-running production experience with webhook migration and Bitbucket Data Center import is limited. - The deprecation notice does not give a definitive removal version for old action-run events. - Runner versions older than 13.2 do not support the new job-summary functionality. ## Sources - [Forgejo v17.0 is available](https://forgejo.org/2026-10-release-v17-0/) — Forgejo · primary · 2026-10-15T00:00:00+13:00. Canonical release announcement with breaking webhook/link semantics, API and LFS improvements, migration support and support schedule. - [Forgejo 17.0 Dev Platform Released with Improved Actions, Git LFS Support](https://linuxiac.com/forgejo-17-0-dev-platform-released-with-improved-actions-git-lfs-support/) — Linuxiac · secondary · 2026-10-15T00:00:00+13:00. Independent specialist reporting confirming scope and practical self-hosted workflow implications. - [Forgejo release schedule](https://forgejo.org/docs/v17.0/admin/release-schedule/) — Forgejo Documentation · primary · 2026-10-15T00:00:00+13:00. Canonical 17.0 and 15.0 LTS support dates.