Forgejo 17.0: repo-relative links, workflow-run webhooks and Bitbucket Data Center migration

Serguey Asael Shinder16 October 2026, 14:023 min read

Forgejo, the community-developed self-hosted platform for code collaboration, released version 17.0 on 15 October 2026. The project's announcement lists a selection of changes and points to the full release notes; it also asks administrators to make a full backup and read the breaking changes before upgrading.

Two changes need attention before an upgrade. In rendered documents, absolute links to resources inside a repository are now resolved against the root of the repository, not the root of the instance (!12939). Absolute links in issue and pull request descriptions and comments are still resolved against the instance root (!13993). Forgejo says the change brings it closer to other Git forges and makes migrations easier. The second item is marked "action required": action run webhook events are deprecated in favour of workflow run events (!14351). Existing webhooks cannot be migrated automatically, because some headers (X--Event, X--Event-Type) and the action key have changed, and completion notifications are only sent after every job in a run has finished (!12598). Administrators are asked to check their receivers and move webhooks over by hand.

Forgejo Actions. The HTTP API can now rerun a whole workflow run (/repos/{owner}/{repo}/actions/runs/{run_id}/rerun) or a single job (.../actions/jobs/{job_id}/rerun) once it has completed (!13924). Job-log endpoints gained substring filters (!12821), a ?step=N parameter to return one step (!12799) and NDJSON output with ?format=ndjson (!12820). Job summaries written by Forgejo Runner 13.2 or newer are now displayed above the logs (!14076); steps write Markdown fragments to $FORGEJO_STEP_SUMMARY, and $GITHUB_STEP_SUMMARY is accepted too. Webhooks can now fire when a workflow job's status changes, with a choice of which statuses to receive (!14334).

Collaboration features. Repositories with a FUNDING.yml file get a "Donate" button, and the same works on user and organisation profiles through the .profile repository. Typing # or ! in an issue, pull request or comment now offers auto-completion (!8088). Organisations can be set to invite new members instead of adding them directly, by setting [service].ADD_MEMBERS_BY_INVITATIONS = true in app.ini; invitations are sent by email and expire after 14 days by default. Users can be added to several teams at once (!11848), maintainers and pull request authors can push directly to AGit refs, and Git LFS support is being reworked, with new views showing which commits refer to an LFS file.

Migrations. Forgejo can now import repositories from Bitbucket Data Center (formerly Bitbucket Server), including pull requests, reviews, multi-line comments, threads and replies (!13288). It authenticates with an HTTP access token and needs "HTTPS SCM Hosting" enabled on the Bitbucket side. Repository avatars are now carried over when migrating from Gogs, GitLab, Gitea or Forgejo (!12921), and the documentation gained a backup-and-restore guide.

Support window. v17.0 is not an LTS release and is supported until 28 January 2027. The current LTS, 15.0, is supported until 15 July 2027; v16.0 reaches end of life on 29 October 2026. The next LTS, 19.0, is planned for 15 April 2027.

Source: Forgejo, "Forgejo v17.0 is available" — https://forgejo.org/2026-10-release-v17-0/