{
  "id": 14791090,
  "title": "Forgejo v17.0 is available",
  "url": "https://urgent.news/2026/10/15/forgejo-v17-0-is-available",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-15T19:43:19.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://forgejo.org/2026-10-release-v17-0/"
  },
  "original_language": "en",
  "account": "Forgejo version 17.0 was launched on October 15, 2026. This release, a lightweight, community-driven self-hosted platform for code collaboration, brings several new features and enhancements. A comprehensive list of changes can be found in the release notes.\n\nTo experiment with the update, a dedicated test instance is available. Before upgrading, it's crucial to back up the entire system and review the breaking changes detailed in the release notes. If clarification is needed, assistance is available in the chat room.\n\nIn the rendered documents, links to resources within a repository are now correctly resolved relative to the repository's root. This change, identified as !12939, breaks compatibility with previous behavior where links were resolved using the instance root. Links in issue and pull request descriptions and comments still point to the instance root.\n\nThis update enhances compatibility with other Git forges, simplifying migrations to Forgejo. The deprecated action run events have been replaced by more robust and flexible workflow run events, identified as !14351. However, migrating existing webhooks to these new events manually is required due to changes in headers and the action key, which could disrupt existing receivers.\n\nUsers of repositories containing a FUNDING.yml file will now see a new \"Donate\" button, offering multiple donation options. For users and organizations with such a file in their .profile repository, a similar button appears on their profile pages. Currently, this feature is only available in the web interface, but an API surface is being considered for future implementation. If you have use cases for this feature, your feedback can be shared in the dedicated issue.\n\nForgejo's issue, pull request, and comment creation processes now feature auto-completion. To activate this feature, type # for issues or pull requests, or ! for pull requests only. Suggestions can be refined by providing a search term or an issue or pull request number.\n\nForgejo's Git LFS support is being reevaluated. While the majority of changes are behind the scenes, users will notice improvements in navigation, overview enhancements in the LFS settings, new views to identify commits referring to a specific LFS file, and improved handling of pointers.\n\nForgejo allows for the configuration of user invitations during organization membership addition. Instead of immediate addition, users receive an invitation to accept or decline. These invitations can be sent via email and are visible on the organization profile. The default expiration period for these invitations is 14 days.\n\nUsers can now be added or invited to multiple teams simultaneously, bypassing the need to add them individually to each team. This capability, identified as !11848, improves efficiency in team management.\n\nThe Forgejo HTTP API has seen multiple enhancements related to Forgejo Actions. Version 13.2 or newer of Forgejo Runner now generates job summaries, displayed above the logs in a Markdown format. These summaries include tables, Mermaid diagrams, and KaTeX formulas. Compatible with both $FORGEJO_STEP_SUMMARY and $GITHUB_STEP_SUMMARY, they offer flexibility for transition from GitHub.\n\nForgejo's webhooks have received numerous updates. They can now trigger when the status of a Forgejo Actions workflow job changes, identified as !14334. Users can customize which statuses, such as \"waiting\" or \"cancelled,\" to receive notifications for. The deprecated \"action runs\" events have been replaced by the new workflow job events.\n\nAuthentication now requires an HTTP access token, and \"HTTPS SCM Hosting\" must be enabled on Bitbucket for Forgejo migrations. During repository migration from Bitbucket Data Center, pull requests, reviews, comments, threads, and replies are preserved. Additionally, repository avatar images from Bitbucket, Gogs, Gitlab, Gitea, or Forgejo are now migrated during the process, as noted in !13288.\n\nForgejo can now import repositories migrated from Bitbucket, Gogs, Gitlab, Gitea, or Forgejo, ensuring a smooth transition. Authentication uses an HTTP access token, necessitating the enabling of \"HTTPS SCM Hosting\" on Bitbucket for successful Forgejo migrations.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}