Forgejo 17.0 is the latest major release covered in this article of the community-developed, self-hosted Git collaboration platform. It provides tools for hosting repositories, reviewing code, managing issues and pull requests, and automating software workflows without depending exclusively on a third-party hosted service.

The release expands Forgejo Actions, improves Git Large File Storage (Git LFS), makes repository migration from Bitbucket Data Center possible, and introduces funding buttons through FUNDING.yml. It also brings changes to organization invitations, team administration, issue and pull request autocomplete, and webhook notifications.

1. What Is Forgejo?

Forgejo is a community-driven, self-hosted platform for Git repositories and collaborative software development. It brings together source-code hosting, pull requests, issues, code review, repository administration, and automation capabilities.

Organizations can run Forgejo on infrastructure they control, making it an option for development teams that want greater control over their source code, access policies, integrations, and deployment environment.

• Host and manage Git repositories.
• Review code and collaborate through pull requests.
• Track work using issues and discussions.
• Automate build, test, and deployment workflows with Forgejo Actions.
• Manage organization membership, teams, and repository permissions.
• Use Git LFS to manage large files associated with repositories.

Forgejo is not simply a Git command-line client. It is a server platform that developers and administrators can integrate into their broader software delivery infrastructure.

2. What’s New in Forgejo 17.0?

These changes are documented in the official Forgejo 17.0 release announcement. Administrators should consult the full release notes for additional details and migration considerations.

3. Forgejo Actions Gets More Powerful

Forgejo Actions is the platform’s integrated CI/CD system. It enables teams to automate tasks such as compiling software, running tests, checking code quality, and publishing build artifacts. Workflow execution is delegated to registered runners rather than being performed directly by the Forgejo server.

Markdown job summaries

Forgejo 17.0 can display job summaries generated by Forgejo Runner 13.2 or newer. These summaries appear above the job logs and can contain supported Markdown features, including tables, Mermaid diagrams, and mathematical formulas.

Workflow steps can write summary content to $FORGEJO_STEP_SUMMARY. The compatible $GITHUB_STEP_SUMMARY variable is also supported, making it easier to adapt existing workflows.

# Example: write a short summary from a workflow step
echo "## Build completed" >> "$FORGEJO_STEP_SUMMARY"
echo "The build and validation steps finished." >> "$FORGEJO_STEP_SUMMARY"

This example illustrates the summary mechanism. Add it to a workflow step that runs in a compatible Forgejo Runner environment; it is not a complete workflow file.

Rerun completed workflows and jobs

The Actions API now supports rerunning completed workflow runs or individual completed jobs. This gives developers more control over retrying failed work without necessarily rerunning an entire pipeline.

More flexible job logs

Job-log endpoints gain substring filtering, step-specific log retrieval, and NDJSON output options. These improvements can help developers investigate failed steps and integrate logs into diagnostic tools.

More granular webhook events

Webhook notifications can now be triggered by changes in individual workflow job statuses. Teams can use these events to notify chat applications or external services about selected job states, including waiting or cancelled jobs.

Official documentation: Forgejo Actions user guide ↗

4. Improved Git LFS Management

Git Large File Storage is useful when repositories contain assets that are not well suited to ordinary Git history, such as large binary files, design assets, media, and certain datasets.

Forgejo 17.0 improves the administration and discovery of LFS files within a repository.

Better LFS navigation

The LFS settings interface receives improved navigation and overview pages, making it easier for repository administrators to inspect stored LFS objects.

Find commits referencing an LFS file

New views help users identify commits that reference a particular LFS file. This is valuable when investigating how large assets are used across a repository’s history.

Improved pointer handling

The release also improves the handling of Git LFS pointers. These small text files reference the underlying large objects rather than containing the objects themselves.

For teams maintaining repositories with large assets, the improvements can make file discovery and troubleshooting more straightforward. They do not remove the need to configure appropriate LFS storage, backups, and retention policies.

5. Repository and Developer Workflow Improvements

Repository funding with FUNDING.yml

Repositories can now display a Donate button when they include a supported FUNDING.yml file. A similar button can appear on user and organization profiles when the relevant profile repository includes the file.

This provides a visible way for open-source projects to present their available funding options. The new functionality is currently exposed through the web interface.

Issue and pull request autocomplete

When writing an issue, pull request, or comment, developers can type a symbol to bring up relevant suggestions:

• # suggests matching issues and pull requests.
• ! restricts suggestions to pull requests.

Typing an additional search term or issue number helps refine the available suggestions.

Copy comment Markdown

Forgejo 17.0 adds an option to copy the Markdown contents of a comment from its menu. This can be helpful when reusing technical instructions, reproducing issue details, or moving discussion content into another document.

Push to AGit references

The release expands support for pushing to AGit references, improving workflows for pull-request creators and maintainers who collaborate through these references. Consult the official announcement for the relevant Git commands and configuration requirements.

6. Repository Migration from Bitbucket Data Center

Forgejo 17.0 introduces repository migration support for Bitbucket Data Center, formerly known as Bitbucket Server. This provides an additional path for organizations that are moving repositories to a self-hosted Forgejo instance.

The migration process can transfer more than the repository contents. Supported information includes:

• Git repository data.
• Pull requests.
• Reviews.
• Comments, including multiline comments.
• Discussion threads and replies.

The documented migration flow uses an HTTP access token, and HTTPS SCM hosting must be enabled on Bitbucket because Forgejo performs the repository migration over HTTPS.

7. Organization and Team Management

Accept-or-decline organization invitations

Administrators can configure Forgejo so that users receive an invitation when being added to an organization instead of being added immediately. Users can accept or decline invitations, which expire after 14 days by default.

This behavior can be enabled in app.ini with the following setting:

[service]
ADD_MEMBERS_BY_INVITATIONS = true

Review the official documentation before changing configuration. Authentication providers may still add users to organizations without requiring this invitation process.

Add users to multiple teams

Administrators can add or invite users to multiple teams in a single operation. This reduces repetitive work when setting up access for a group of developers or onboarding team members.

Repository avatar migration

Repository avatar images are also migrated when moving repositories from supported platforms, including Gogs, GitLab, Gitea, and Forgejo.

8. Breaking Changes and Upgrade Warnings

Forgejo 17.0 includes changes that administrators should review before upgrading an existing instance.

Absolute links in rendered documents

Absolute links to resources inside a repository are now resolved relative to that repository’s root when rendered in repository documents. This differs from the previous behavior, where these links were resolved relative to the Forgejo instance root.

Links in issue and pull request descriptions and comments continue to be resolved relative to the instance root. Review documentation and repository content that relies on the previous behavior.

Action-run webhook events are deprecated

The older action-run webhook events are being replaced by workflow-run events. Existing webhook receivers may need changes because event headers and payload fields differ. Completion notifications are also emitted only after all jobs in a run have terminated under the new behavior.

Administrators should inspect existing webhooks, update their event subscriptions and receiver logic, and test notifications before upgrading production workloads.

Back up before upgrading

The Forgejo project recommends taking a full backup and carefully reviewing the breaking changes before upgrading. Ensure that the backup covers the data, configuration, and secrets required to restore the instance correctly.

9. Download Forgejo 17.0

Forgejo provides official download instructions for Linux binaries and container images. Select the package that matches your architecture and deployment method.

Forgejo binaries are signed with the project’s GPG key. Follow the official instructions to obtain the corresponding signature and verify the downloaded binary before deploying it.

10. Installation Overview

Forgejo can be deployed using a binary or a container image. The appropriate method depends on your Linux distribution, container runtime, database, storage, reverse proxy, and operational requirements.

Example: Download the Linux AMD64 binary

The following commands demonstrate downloading the official v17.0.0 binary and making it executable. They are not a complete production installation procedure.

wget https://code.forgejo.org/forgejo/forgejo/releases/download/v17.0.0/forgejo-17.0.0-linux-amd64

chmod +x forgejo-17.0.0-linux-amd64

./forgejo-17.0.0-linux-amd64 --version

Check the official documentation for the recommended service account, directory permissions, configuration, database setup, reverse proxy, and service-management instructions. Verify the GPG signature before executing a downloaded binary.

Before deploying in production

1. Choose the correct architecture and installation method.
2. Verify the binary or image using official project guidance.
3. Prepare persistent storage and database configuration.
4. Configure HTTPS, authentication, permissions, and backups.
5. Set up Forgejo Runner separately where CI/CD execution is required.
6. Test Actions workflows, Git LFS, webhooks, and repository access.
7. Document your restore procedure and monitor the instance after deployment.

Read Forgejo 17.0 documentation ↗

11. Release Lifecycle and Support

Forgejo 17.0 is a non-LTS release with support scheduled to end on January 28, 2027. Administrators who prefer a longer maintenance period can consider the project’s Forgejo 15.0 LTS line, which is scheduled for support until July 15, 2027.

Review the project’s current release and lifecycle information before choosing a production version. Support dates and patch availability should be checked against the official project site at upgrade time.

12. Frequently Asked Questions

13. Official Sources and References

• Forgejo — Version 17.0 Release Announcement
• Forgejo — Official Download Instructions
• Forgejo 17.0 Documentation
• Forgejo Actions — User Guide
• Forgejo — Project News and Updates
• Linuxiac — Forgejo 17.0 Release Coverage

Share this article

Disclaimer: Forgejo is an independent open-source project. VMoreCloud is not affiliated with or endorsed by Forgejo. Always consult the official release notes and documentation before upgrading production systems. Third-party product names are used for identification and compatibility discussion.