1216 lines
111 KiB

# Release Notes
A Forgejo release is published shortly after a Gitea release is published and they have [matching release numbers]( Additional Forgejo releases may be published to address urgent security issues or bug fixes.
The Forgejo admin should carefully read the required manual actions before upgrading. A point release (e.g. v1.21.1-0 or v1.21.2-0) does not require manual actions but others might (e.g. v1.20, v1.21).
## 1.21.0-0 (DRAFT)
The [complete list of commits]( included in the `Forgejo v1.21.0-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges origin/v1.20/forgejo..origin/v1.21/forgejo
- **[Forgejo Semantic Version](**
The semantic version was updated to `6.0.0+0-gitea-1.21.0` because it contains breaking changes.
- **Breaking:**
Note that the modifications related to CSS, templates or assets (images, fonts, etc.) are not documented here.
Although they can be extracted and modified, Forgejo does not provide any guarantee that such changes
will be portable from one version to another (even a patch version).
- [Restrict certificate type for builtin SSH server]( This is a breaking change for setups where the builtin SSH server is being used and for some reason host certificates were being used for authentication.
- [Some Forgejo CLI options have changed]( and scripts may need to be updated. For instance `--verbose` is no longer a global option and is implemented on a per sub-command basis. Check `forgejo --help` or `forgejo docs` for more information.
- [Remove "CHARSET" config option for MySQL and always use "utf8mb4"]( It has been a requirement for years and specifying anything else is likely to cause issues.
- [Set SSH_AUTHORIZED_KEYS_BACKUP to false by default]( There is no automatic cleanup of these backups and can end up using a significant amount of disk space over time.
(More items to be added here)
## 1.20.4-1
The [complete list of commits]( included in the `Forgejo v1.20.4-1` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.20.4-0..v1.20.4-1
This stable release includes bug fixes.
* Recommended Action
We recommend that all Forgejo installations are [upgraded]( to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated to `5.0.4+0-gitea-1.20.4`
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Fix the followers and following list that only showed the first page](
* [Fix issue templates preventing the creation of any new issues when blank issues are not authorized]( (regression introduced in v1.20.4-0)
## 1.20.4-0
The [complete list of commits]( included in the `Forgejo v1.20.4-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.20.3-0..v1.20.4-0
This stable release includes bug fixes and two features.
* Recommended Action
We recommend that all Forgejo installations are [upgraded]( to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated to `5.0.3+0-gitea-1.20.4`
* Features
* [Log slow SQL queries]( to help identify bottlenecks on large Forgejo instances
* [Add `branch_filter` to hooks API endpoints](
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Ignore the trailing slashes when comparing oauth2 redirect_uri](
* [Fix the reopen logic for agit flow pull request](
* [Fix the missing display of user projects](
* [Fix]( issue templates [that failed to save checkboxes](
* [Fix accessibility issues preventing focus and selection](
* [Fix being unable to use a repo that prohibits accepting PRs as a PR source](
* [Forgejo doctor database fix]( to repair a condition preventing the owner of an organization from creating a repository
* [Fix dashboard filters having no effect](
* [Also check the email blocklists when adding new emails to existing accounts](
* [Sync tags when adopting repos](
* [Fix an error when pushing a new branch and there is a requirement that all commits are signed](
## 1.20.3-0
The [complete list of commits]( included in the `Forgejo v1.20.3-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.20.2-0..v1.20.3-0
This stable release includes bug fixes and a safeguard against a
regression that may lead to data loss. The `[storage*]` sections in the
`app.ini` file may cause the files for some subsystems - Attachments,
LFS, Avatars, Repository avatars, Repository archives, Packages - to
be merged together or misplaced. The safeguard detects this situation
and Forgejo will not start to prevent data loss. If your instance is in
this situation, [follow the instructions in the companion blog post](
* Recommended Action
We recommend that all Forgejo installations are upgraded to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated to `5.0.2+0-gitea-1.20.3`
* Breaking changes
* [Fix some bugs in how the storage sections are interpreted]( in the `app.ini` file. Read more about this issue in the [v1.20.3-0 blog post](
* [Add sanity checks]( to detect an `app.ini` configuration that [needs manual fixing to preserve storage](
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Fix links to pull request reviews sent via mail]( The pull request link was correct but it did not go the the review and stayed at the beginning of the page
* [Recognize OGG as an audio format](
* [Consistently show the last time a cron job was run in the admin panel](
* [Fix NuGet registry v2 & v3 API search endpoints](
* [Allow html <img /> code to be parsed in markdown files](
* [Fix incorrect color of the selected assignees when creating an issue](
* [Add missing MinIO region on client initialization](
* [Add pull request review request webhook event](
* [Fix bad url in the wiki due to incorrect unescaping](
* [Fix the sort menu that was broken when displaying a custom profile from the `.profile` repository](
* [Workaround]( MariaDB [performance issue on large Forgejo instances](
* [Display human-readable text]( instead of [numerical file modes](
* [The CLI exit code now is different from zero when an error occurs](
* [Fix error when a Debian package has a double newline character at the end of the control block](
* [Fix a condition that would cause git related tasks to hang for longer than necessary in the queues and use too many resources as a result](
* [Fix the topic validation rule and suport dots](
* [Fix pull request check list when there are more than 30](
* [Fix attachment clipboard copy on insecure origin](
* [Fix the profile README rendering]( that [was inconsistent with other markdown files renderings](
* [Fix API leaking the user email when the caller is not authentified](
## 1.20.2-0
The [complete list of commits]( included in the `Forgejo v1.20.2-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.20.1-0..v1.20.2-0
This stable release includes bug fixes and displays [warnings in the administration panel]( when deprecated entries are found in `app.ini`.
* Recommended Action
We recommend that all Forgejo installations are upgraded to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated to `5.0.1+0-gitea-1.20.2`
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Add missing assets to the Forgejo sources tarbal](
* [Fix user type selection error when creating a user]( and selecting `public` or `private`.
* [Fix access check for org-level project](
* [Warn instead of reporting an error when a webhook cannot be found](
* [Set MAX_WORKERS]( to a value lower than 10 if the number of available CPUs is low to avoid overloading the host.
* [Fix bug when pushing to a pull request which enabled dismiss approval automatically](
* [Fix handling of plenty Nuget package versions](
* [Update](
* [Fix bugs]( in [LFS meta garbage collection](
* [Fix UI regression of asciinema player](
* [Fix LFS object list style](
* [Fix CLI allowing creation of multiple user access tokens with the same name](
* [Fix]( router logger [preventing separating the logs in different files](
* [added ssh mirror workaround description](
* [Fix wrong workflow status when rerun a job in an already finished workflow](
* [Fix escape problems in the branch selector](
* [Fix handling of Debian files with trailing slash](
* [fix Missing 404 swagger response docs for /admin/users/{username}](
* [Use stderr as fallback if the log file can't be opened](
## 1.20.1-0
The [complete list of commits]( included in the `Forgejo v1.20.1-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges origin/v1.19/forgejo..origin/v1.20/forgejo
- **[Forgejo Semantic Version](**
The semantic version was updated to `5.0.0+0-gitea-1.20.1` because it contains breaking changes.
- **Breaking:**
- [Scoped access tokens]( or (Personal Access Tokens), were refactored and although existing tokens are still valid, they may have a different scope than before. To ensure that no tokens have a larger scope than expected they must be removed and recreated.
- If your `app.ini` has one of the the following `[indexer].ISSUE_INDEXER_QUEUE_TYPE`, `[indexer].ISSUE_INDEXER_QUEUE_BATCH_NUMBER`, `[indexer].`, `[indexer].ISSUE_INDEXER_QUEUE_DIR`, `[indexer].ISSUE_INDEXER_QUEUE_CONN_STR`, `[indexer].UPDATE_BUFFER_LEN`, `[mailer].SEND_BUFFER_LEN`, `[repository].PULL_REQUEST_QUEUE_LENGTH` or `[repository].MIRROR_QUEUE_LENGTH`, Forgejo will abort immediately. Unless you know exactly what you're doing, you must comment them out so the default values are used.
- The `-p` option of `environment-to-ini` is [no longer supported](
- The ".png" suffix for [user and organizations is now reserved](
- The section `[git.reflog]` is [now obsolete and its keys have been moved]( to the following replacements:
* `[git.reflog].ENABLED``[git.config].core.logAllRefUpdates`
* `[git.reflog].EXPIRATION``[git.config].gc.reflogExpire`
- The [logger]( used to display Forgejo's was refactored and has new settings, different from the previous one found at `log.<mode>.<logger>` in `app.ini`. Check the [documentation]( and `app.example.ini` for more information. The SMTP logger was removed.
- Forgejo will refuse to start if [the refactored path & config system]( does not pass sanity checks (e.g. WORK_PATH must be absolute).
- Manually set [WORK_PATH]( in `app.ini`.
If the `app.ini` file is writable by the user under which the Forgejo server runs and `WORK_PATH` is not set,
the server will add it. Otherwise it will log an error starting with `Unable to update WORK_PATH`.
One of the consequences of not setting `WORK_PATH` in `app.ini` is that pushing to a repository via ssh is
[likely to fail as explained in the corresponding bug report](
Read the technical details in the [commit that implements the WORK_PATH change](
- The user profile can be customized with [a Markdown file](
The profile page of a user is rendered using the `` file of the `.profile` repository, if it exists. It is a
breaking change because **it will display the .profile/ of a pre-existing repository, private or not**.
- The [API endpoint pagination]( for team members was fixed: it now starts at 1 instead of 0, just like all other paginated API endpoints.
- The `SSH_KEYGEN_PATH` variable in `app.ini` now defaults to using the [Go SSH key parsing instead of the `ssh-keygen` binary]( When `START_SSH_SERVER` is true, the decision to use the Go SSH key parsing or an external binary will now depend on the value of `SSH_KEYGEN_PATH` instead of always using the Go SSH key parsing.
- The storage settings were [refactored]( Read more about [storage settings](
- [The [repository.editor] PREVIEWABLE_FILE_MODES setting was removed]( This setting served no practical purpose and was not working correctly. Instead a preview tab is always shown in the file editor when supported.
- In addition to the already deprecated options inside [queue], many options have been dropped as well. Those are WRAP_IF_NECESSARY, MAX_ATTEMPTS, TIMEOUT, WORKERS, BLOCK_TIMEOUT, BOOST_TIMEOUT, BOOST_WORKERS. You can remove them from your app.ini now. Additionally, some default values have changed in this section.
- The default CSS and templates included in Forgejo were heavily refactored and a large number of variables renamed. These changes are not documented and there is a very high chance that a tempate extracted and modified for a particular Forgejo instance will no longer work as it did. Browsing through the git history of the template in the sources is the best way to figure out how and why it was modified.
- **Moderation:**
Blocking another user is desirable if they are acting maliciously or are spamming your repository. When you block a user, Forgejo does not explicitly notify them, but they may learn through an interaction with you that is blocked. [Read more about blocking users](
- **Package:**
New registries are available for [SWIFT](, [debian](, [RPM](, [alpine](, [Go]( and [CRAN](
- **Accessibility:**
numerous improvements for [issue comments](, [the menu on the navbar](, [scoped labels](, [checkboxes and dropdowns](, [RTL rendering support to Markdown](, [file (re-)views](, [interactive tooltips](, [using a button element](, [repository list]( and more.
- **Time:**
The display and localization of time was improved for [tooltips](, [milestones](, [due date and translations that contain dates](, [commit graphs](, [runners](, [webhooks](, [tests]( and more. Previously each rendered timestamp would be static, now the real time since an event happend is show. If a comment was added 2 minutes before the page rendered it would show as "2 minutes ago" on the initial render and if another 8 minutes have passed, without a page refresh you'd see "10 minutes ago".
- **[Wiki](**
- Improve the [display of the table of content](
- Fixed a bug [preventing team users who have wiki write permission from deleting a page](
- [Shows the External Link icon and URL in the header]( to indicate that the user will be sent to an external side to help prevent fishing
- Allow dash in [titles](
- **[Actions](**
- The internal CI graduated from **experimental** to **[alpha](**. It now has with a [user]( documentation that includes examples and an extensive [administrator]( guide to set it up.
- [Forgejo Actions]( workflows are [now available]( to run tests and publish releases for `Forgejo` itself.
- The Woodpecker CI configuration for PR verification and building releases for Forgejo v1.18 and v1.19 is no longer maintained as part of Forgejo itself and was moved to its [own repository](
- **[Templates](**
- [Configuration for the issue templates]( [Read more about issue config]( in the documentation.
- [Add validations.required check to the dropdown field](
- [Issue template support markdown edition](
- [Use a general Eval function for expressions in templates](
- [reload-templates CLI](
- **User Interface and User eXperience**
- The web editor used when creating issues, adding comments, etc. [changed]( from [EasyMDE]( which was no longer actively maintained to [GitHub markdown]( To help with the transition it is still possible to switch back to using EasyMDE using the double arrow button in the menubar.
- [Improve wiki sidebar and TOC](
- [Show outdated comments in the files changed tab of a pull request review](
- [Redirect to package after version deletion](
- Use a [separate admin page to show stats](
- [Improve avatar compression and resizing](
- [Add button to compare force pushed commits in pull requests](
- [When creating a new file in a repository via the web user interface allow for a path to be pasted](
- [Allows "video" HTML tag to be used in MarkDown, with the src, autoplay, and controls attributes](
- [Add "Reviewed by you" filter for pull requests](
- [Make Ctrl+Enter submit a pending comment (starting review) instead of submitting a single comment](
- If an instance chooses to disable new pull or push mirrors or mirrors entirely, an appropriate message will [now be shown to the user in the Repository Settings](
- [Change `Close` to either `Close issue` or `Close pull request`](
- [Make Issue/PR/projects more compact](
- [Improve RSS user interface](
- [Add details summary for vertical menus in settings to allow toggling](
- [Show visibility status of email in own profile](
- [Improve the protected branch setting page](
- [Improve the display of the pull request branch delete button](
- [Fix the color for repository transfer related buttons when having no permission to act](
- [Add a progressbar to Milestone Page](
- [Nicer display when the list of notifications is empty](
- [Rename board to column in projects](
- [Improve header bar on issue, pull requests and milestone](
- [Add organization visibility label when displayed on the dashboard](
- [Unification of registration fields order](
- [Append `(comment)` when a link points at a comment rather than the whole issue](
- [Add visibility (private, limited) in the dashboard navbar](
- [Show all activities in the dashboard, not just the most recent ones](
- [Do not display the stars in the repository list of the dashboard](
- [Improve the display of tags to include the tag message](
- [Hide the target selector if a tag exists when creating a new release](
- [Show the calculated commit status state of the latest commit on the default branch for each repository in the dashboard repository list](
- [Sort users and orgs on the explore page by recency](
- [Show the number of repositories in the user or organization profile](
- [Review management (requesting again and discard) now happens at the top of the pull request](
- [Add markdown preview when submitting a review](
- [Support no label/assignee filter and batch clearing labels/assignees](
- [Display when a repo was archived](
- [Improve squash merge commit author and co-author with private emails](
- [Allow adding new files to an empty repo](
- [Move `Rename branch` from repo settings page to the page of branches list](
- [Add "Updated" column for admin repositories list](
- [Hide the merge box of a pull request if it is merged and the branch was deleted](
- [The repository migration can be canceled](
- [Add button on the diff header to copy the file name](
- [Add --quiet option to the dump CLI](
- [Support searching for an issue with its number in the the list of issues](
- [Improve the list of notifications](
- [When editing a file in the web UI, allow for a preview whenever possible](
- [Make release download URLs human readable](
- [Add a tooltip to `Publish Review` explaining why they are disabled](
- [Show the file tree view by default when browsing the changes in a pull request](
- [Allow both fullname search in the author dropdown search of the issue list when `DEFAULT_SHOW_FULL_NAME` is true](
- **Performance**
- [Improve performances when listing issues](
- [Speedup loading the list of authors in the dropdown of the list of issues](
- [Use minio/sha256-simd for accelerated SHA256](
- [Speed up HasUserStopwatch & GetActiveStopwatch](
- [Do not create commit graph for temporary repos](
- [Faster git.GetDivergingCommits](
- [Order pull request conflict checking by recently updated, for each push](
- [MySQL integration tests]( run twice faster low end machines and use an order of magnitude less disk I/O
- **Authentication**
- [Add ntlm authentication support for mail](
- [LDAP filters include both username and email address](
- [Allow for PKCE flow without client secret](
- [Add the ability to set multiple redirect URIs in the OAuth application UI](
- **Refactor:**
Many essential sub-systems were refactored: the [queue system]( that handles background tasks such as checking pull requests, [pull mirror](, [git internal API](, [routes]( and [web routes](, [merge & update logic]( and [git command calls](, [listing commits](, [cookie](, [issue stats](, [renaming users and organizations](, [app.ini handling](, [diffFileInfo / DiffTreeStore]( In theory these changes are transparent to the Forgejo user and admin but the risk of subtle regressions is real: do not hesitate to [reach out]( if you suspect anything.
- **RSS**
- [Support "." char as user name for User/Orgs in RSS/ATOM/GPG/KEYS](
- [Add RSS Feeds for branches and files](
- **API**
- [Add admin API for email](
- [Add admin API to rename a user](
- [Add login name and source id to admin user searching API](
- [Add missing units to create and edit repo API](
- [Add API to manage issue dependencies](
- [Add API for activity feeds](
- [Add API for license templates](
- [Add API for gitignore templates](
- [Add API to upuload a file to an empty repository](
- [Allow for --not when listing the commits of a repo](
- [Add `files` and `verification` parameters to improve performances when listing the commits of a a repo](
- [Allow for listing a single commit in a repository](
- [Create a branch directly from commit on the create branch API](
- [Add API for Label templates](
- [Add API for changing/creating/deleting multiple files](
- **Miscellaneous Features**
- [Any URL scheme may be used for links]( Previously, non-standard URLs (like matrix:) were not rendered unless explicitly listed in `markdown.CUSTOM_URL_SCHEMES`. Now the default if `markdown.CUSTOM_URL_SCHEMES` is not set, all schemes are allowed and markdown links ([label](URL)) render as links.
- [Always use "utf8mb4" for MySQL](
- [Add Adopt repository event and handler](
- Add [meilisearch]( support to [index the content of repositories](
- [Add support]( for [redis v7](
- Allow [webp]( images [as avatars](
- [Add support]( for rendering [.livemd](
- The `forgejo forgejo-cli actions` [subcommand is added]( to implement [offline registration with `actions register`]( for the [Forgejo runner](
- When [called as `forgejo-cli`]( (with `ln -f forgejo forgejo-cli`), Forgejo provides a new CLI that is not backward compatible with Gitea. It contains Forgejo specific additions such as [offline registration](
- [Render list items]( when an [org-mode]( file is displayed
- [A user can follow an organization](
- [When playing a video in the web UI, the player control can be dragged to play on the specified position](
- The commit status required for a pull request to be merged can now be [specified as patterns]( instead of being a hard coded list
- [Support wildcard in email domain allow and block lists]( [Read more about EMAIL_DOMAIN_ALLOWLIST and EMAIL_DOMAIN_BLOCKLIST](
- When [installing with docker]( the value of a configuration variable can now be fetched from a file by [adding the `__FILE` suffix]( For instance `FORGEJO__security__INTERNAL_TOKEN__FILE=/etc/forgejo/token` can be used instead of `FORGEJO__security__INTERNAL_TOKEN=tokenvalue`.
- The [new `[git.config]` section of `app.ini`]( is used to `git set config`. [Read more about the defaults it contains](
- [Issues and pull requests can be pinned]( They will show on top of the list of issues (or pull requests) and can be re-arranged by dragging them.
- [Implement systemd-notify protocol]( and allows for using `Type=notify` in service files.
- [Provide more control over the repositories that are indexed]( [Read more about REPO_INDEXER_REPO_TYPES](
- **Webhook**
- Similar to organization wide webhooks, it is now possible to have [user wide webhooks](
- [Add webhook trigger when a Pull Request review requests is created](
* Container images upgraded to Alpine 3.18
The Forgejo container images are now based on [Alpine 3.18]( instead of Alpine 3.17.
## 1.19.4-0
The [complete list of commits]( included in the `Forgejo v1.19.4-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.19.3-0..v1.19.4-0
This stable release contains security fixes.
* Recommended Action
We recommend that all Forgejo installations are upgraded to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated from `4.2.1+0-gitea-1.19.3` to `4.2.2+0-gitea-1.19.4`.
* Security fixes
* [An additional verification]( was implemented to prevent [open redirects](
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Fix an edge case]( where a user changing their `username` in their profile page could fail
* The secrets are only meaningful in the context of `Frogejo Actions`, do not display them if `Forgejo Actions` is disabled ([patch 1](, [patch 2](
* Actions can now be triggered on mirrored repositories ([patch 1](, [patch 2](
* [Return `404` in the API if the requested webhooks were not found]( instead of `500`
* Ensure topics deleted via the API are [also deleted in the repository](
* [Tentative fix]( to suppress the JavaScript error **TypeError: undefined is not an object (evaluating '_i18n.textEdited')** on safari. It is unclear if that fix is effective because it could not be reproduced, please report if it still happens for you.
* [Respect original content when creating secrets](
* If a mirror failed and left the database in an inconsistent state, make it so the repository page [does not fail with an error `500`](
* If a user that triggered `Actions` is deleted, [allow for the page listing the tasks it launched to show]( instead of failing with an error `500`
* [Allow the selection of milestones]( when acting on multiple issues in the issue list page
* [Fix the API error message when trying to create a fork that already exists](
* [Don't display a `create page` button in a mirror wiki repository]( A mirrored repository will also mirror a wiki and changes will be overridden.
* [Do not allow for a repository to enable actions if it is not enabled in the configuration](
* Allow for closed PRs to be re-opened and [synchronize with the latest content of the head branch](
* [Fix the `close` button of projects within an organization]( It was a noop and now effectively closes the project
## 1.19.3-0
The [complete list of commits]( included in the `Forgejo v1.19.3-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.19.2-0..v1.19.3-0
This stable release contains security fixes.
* Recommended Action
We recommend that all Forgejo installations are upgraded to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated from `4.2.0+0-gitea-1.19.2` to `4.2.1+0-gitea-1.19.3` because of the rebuild with [Go version 1.20.4](
* Security fixes
* Forgejo was recompiled with Go version v1.20.4 published 2 May 2023. It fixes [three vulnerabilities]( ([CVE-2023-29400](, [CVE-2023-24540](, [CVE-2023-24539]( related to the [html/template]( package. The [Forgejo security team]( analyzed the security fixes it contains and concluded that Forgejo is not affected but recommended a rebuild as a precaution.
* Bug fixes
The most prominent one is described here, others can be found in the list of commits included in the release as described above.
* [Allow users that are not signed in to browse the tag list]( Requiring users to be signed in to view the tag list was a regression introduced in Forgejo v1.19.2-0.
## 1.19.2-0
The [complete list of commits]( included in the `Forgejo v1.19.2-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.19.1-0..v1.19.2-0
This stable release contains **important security fixes**.
* Recommended Action
We **strongly recommend** that all Forgejo installations are upgraded to the latest version as soon as possible.
* [Forgejo Semantic Version](
The semantic version was updated from `4.1.0+0-gitea-1.19.1` to `4.2.0+0-gitea-1.19.2` because of the changes introduced in the internal CI.
* Security fixes
* Token scopes were not enforced in some cases ([patch 1]( and [patch 2]( The [scoped token]( were introduced in Forgejo v1.19 allow for the creation of application tokens that only have limited permissions, such as creating packages or accessing repositories. Prior to Forgejo v1.19 tokens could be used to perform any operation the user issuing the token could.
* [Permissions to delete secrets was not enforced]( The experimental internal CI relies on secrets managed via the web interface, for instance to communicate credentials to a job. Secrets are only used in the context of the experimental internal CI.
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Restore public access to some API endpoints]( When [scoped token]( introduced in Forgejo v1.19, some API endpoints that were previously accessible anonymously became restricted: `/orgs`, `/orgs/{org}`, `/orgs/{org}/repos`, `/orgs/{org}/public_members`, `/orgs/{org}/public_members/{username}`, `/orgs/{org}/labels`.
* [Fix 2-dot direct compare to use the right base commit]( For 2-dot direct compare, the base commit should be used in the title and templates, as is used elsewhere, not the common ancestor which is used for 3-dot compare.
* [Make CORS work]( No [CORS]( headers were set, even if CORS was enabled in the configuration.
* [Fix issue attachment removal]( When an attachment was removed from an issue or review comment, all of the image/attachment links were broken.
* [Fix wiki write permissions for users who do not have repository write permissions]( When a team member had write access to the wiki but not to the code repository, some operations (deleting a page for instance) were denied.
* [Respect the REGISTER_MANUAL_CONFIRM setting when registering via OAuth]( Contrary to the local registration, the OAuth registration flow activated a newly registered user regardless of the value of `REGISTER_MANUAL_CONFIRM`.
* [Fix tags list for repos whose release setting is disabled]( When releases was disabled the "tags" button led to a `Not Found` page, even when tags existed.
* Container image upgrades
In the Forgejo container images the Git version was upgraded to [2.38.5]( as a precaution. The [Forgejo security team]( analyzed the security fixes it contains and concluded that Forgejo is not affected.
## 1.19.1-0
The [complete list of commits]( included in the `Forgejo v1.19.1-0` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.19.0-3..v1.19.1-0
This stable release includes bug fixes. Functional changes related to the experimental CI have also been backported.
* Recommended Action
We recommend that all installations are upgraded to the latest version.
* [Forgejo Semantic Version](
The semantic version was updated from `4.0.0+0-gitea-1.19.0` to `4.1.0+0-gitea-1.19.1` because of the changes introduced in the internal CI.
* Bug fixes
The most prominent ones are described here, others can be found in the list of commits included in the release as described above.
* [Fix RSS/ATOM/GPG/KEYS path for users (or orgs) with a dot in their name]( It is allowed for a user (or an organization) to have a dot in their name, for instance ``. Because of a [bug in Chi]( it was not possible to access `/`, `/`, etc. A workaround was implemented while a [proper fix is being discussed](
* [Creating a tag via the web interface no longer requires a title](
* [Use fully qualified URLs in Dockerfile]( The Dockerfile to create the Forgejo container image now uses the fully qualified image `` instead of `golang:1.20-alpine3.17`. This allows for building on platforms that don't have docker hub as the default container registry.
* [Redis use Get/Set instead of Rename when Regenerate session id]( The old sid and new sid may be in different redis cluster slot.
* [Do not escape space between PyPI repository url and package name]( It also adds a trailing slash to the PyPI repository URL in accordance to [Python PEP-503](
* [Fix failure when using the API and an empty rule_name to protect a branch]( The `rule_name` parameter for the [/repos/{owner}/{repo}/branch_protections]( API now defaults to the branch name instead of being empty.
* [Fix branch protection priority]( Contrary to [the documentation]( it was possible for a glob rule to take precedence over a non-glob rule.
* [Fix deleting an issue when the git repo does not exist]( If a project had an issue tracker (such as the [Forgejo discussion]( but [no git repository](, trying to delete an issue would fail.
* [Fix accidental overwriting of LDAP team memberships]( If an LDAP user is a member of two groups, the LDAP group sync only matched the last group.
## 1.19.0-3
The [complete list of commits]( included in the `Forgejo v1.19.0-3` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges v1.19.0-2..v1.19.0-3
This stable release includes security updates and bug fixes.
* Recommended Action
We recommend that all installations are upgraded to the latest version.
* Security
The [Forgejo security team]( analyzed the vulnerabilities fixed in the latest [Go 1.20.3 packages]( and [Alpine 3.17.3]( and concluded that Forgejo is not affected.
As a precaution the Forgejo v1.19.0-3 binaries were compiled with [Go 1.20.3 packages]( as published on 4 April 2023 and the container images were built with [Alpine 3.17.3]( as published on 29 March 2023.
* [Forgejo Semantic Version](
The semantic version was updated from `3.0.0+0-gitea-1.19.0` to `4.0.0+0-gitea-1.19.0` because of the breaking changes described below.
* Breaking changes
They should not have a significant impact because they are related to experimental features (federation and CI).
* [Use User.ID instead of User.Name in ActivityPub API for Person IRI](
The ActivityPub id is an HTTPS URI that should remain constant, even if
the user changes their name.
* [Actions unit is repo.actions instead of actions.actions](
All instances of `actions.actions` in the `DISABLED_REPO_UNITS` or `DEFAULT_REPO_UNITS` configuration variables must be replaced with `repo.actions`.
* Bug fixes
They are for the most part about user interface and actions. The most prominent ones are:
* [Do not filter repositories by default on the explore page]( The behavior of the explore page is back to what it was in Forgejo v1.18. Changing it was confusing.
* [Skip LFS when disabled in dump and doctor](
* [Do not display own email on the profile](
* [Make minio package support legacy MD5 checksum](
* [Do not triggers Webhooks and actions on closed PR](
## 1.19.0-2
The [complete list of commits]( included in the `Forgejo v1.19.0-2` release can be reviewed from the command line with:
$ git clone
$ git -C forgejo log --oneline --no-merges origin/v1.18/forgejo..origin/v1.19/forgejo
* Breaking changes
* [Scoped access tokens](
Forgejo access token, used with the [API]( can now have a "scope" that limits what it can access. Existing tokens stored in the database and created before Forgejo v1.19 had unlimited access. For backward compatibility, their access will remain the same and they will continue to work as before. However, **newly created token that do not specify a scope will now only have read-only access to public user profile and public repositories**.
For instance, the `/users/{username}/tokens` API endpoint will require the `scopes: ['all', 'sudo']` parameter and the `forgejo admin user generate-access-token` will require the `--scopes all,sudo` argument obtain tokens with ulimited access as before for admin users.
[Read more about the scoped tokens](
* [Disable all units except code and pulls on forks](
When forking a repository, the fork will now have issues, projects, releases, packages and wiki disabled. These can be enabled in the repository settings afterwards. To change back to the previous default behavior, configure `DEFAULT_FORK_REPO_UNITS` to be the same value as `DEFAULT_REPO_UNITS`.
* [Filter repositories by default on the explore page](
The explore page now always filters out repositories that are considered not relevant because they are either forks or have no topic and not description and no icon. A link is shown to display all repositories, unfiltered.
<img src="./releases/images/forgejo-v1.19-relevant.png" alt="Explore repositories" width="600" />
* [Remove deprecated DSA host key from Docker Container](
Since OpenSSH 7.0 and greater similarly disable the ssh-dss (DSA) public key algorithm, and recommend against its use.
* Additional restrictions on valid user names
The algorithm for validating user names was modified and some users may have invalid names. The command `forgejo doctor --run check-user-names` will list all of them so they can be renamed.
If a Forgejo instance has users or organizations named `forgejo-actions` and `gitea-actions`, they will also need to be renamed before the upgrade. They are now reserved names for the experimental internal CI/CD named `Actions`.
* [Semantic version](
Since v1.18.5, in addition to the Forgejo release number, a [semantic version]( number (e.g. `v3.0.0`) can be obtained from the `number` key of a new `/api/forgejo/v1/version` endpoint.
Now, it reflects the Gitea version that Forgejo depends on, is no longer prefixed with `v` (e.g. `3.0.0+0-gitea-1.19.0`), and can be obtained from the `version` key of the same endpoint.
* Features
* [Documentation](
The first version of the [Forgejo documentation]( is available and covers the administration of Forgejo, from installation to troubleshooting.
[Read more about semantic versions](
* [Webhook authorization header](
Forgejo webhooks can be configured to send an [authorization header]( to the target.
[Read more about the webhook authorization header](
* [Incoming emails](
You can now set up Forgejo to receive incoming email. When enabled, it is now possible to reply to an email notification from Forgejo and:
* Add a comment to an issue or a pull request
* Unsubscribe to the notifications
[Read more about incoming emails](
* Packages registries
* Support for [Cargo](, [Conda]( and [Chef](
* [Cleanup rules](
* [Quota limits](
* [Option to prohibit fork if user reached maximum limit of repositories](
It is possible for a user to create as many fork as they want, even when a quota on the number of repositories is imposed. The new `ALLOW_FORK_WITHOUT_MAXIMUM_LIMIT` setting can now be set to `false` so forks are prohibited if that means exceeding the quota.
[Read more about repository configurations](
* [Scoped labels](
Labels that contain a forward slash (**/**) separator are displayed with a slightly different color before and after the separator, as a visual aid. The first part of the label defines its "scope".
[Read more about scoped labels](
* [Support org/user level projects](
It is now possible to create projects (kanban boards) for an organization or a user, in the same way it was possible for an individual repository.
* [Map OIDC groups to Orgs/Teams](
When a user logs in Forgejo using an provider such as [Keycloak](, they can now automatically be part of a Forgejo team, depending on the OIDC group they belong to. For instance:
{"Developer": {"MyForgejoOrganization": ["MyForgejoTeam1", "MyForgejoTeam2"]}}
Means that the user who is in the OIDC group `Developer` will automatically be a member of the `MyForgejoTeam1` and `MyForgejoTeam2` teams in the `MyForgejoOrganization` organization.
This mapping is set when adding a new `Authentication Source` in the `Site Administration` panel.
<img src="./releases/images/forgejo-v1.19-oidc-part1.png" alt="OIDC Group mapping part1" width="500" />
<img src="./releases/images/forgejo-v1.19-oidc-part2.png" alt="OIDC Group mapping part2" width="500" />
[Read more about OIDC groups mapping](
* [RSS feed for releases and tags](
A RSS feed is now available for releases at `/{owner}/{repo}/releases.rss` and tags at `/{owner}/{repo}/tags.rss`.
* [Supports wildcard protected branch](
Instead of selecting a branch to be protected, the name of the branch must be specified and can be a pattern such as `precious*`.
[Read more about branch protection](
* [Garbage collect LFS](
Add a doctor command for full garbage collection of LFS: `forgejo doctor --run gc-lfs`.
* Additions to the API
* [Management for issue/pull and comment attachments](
* [Get latest release](
* [System hook](
* [Option to disable releases on a repository](
It is now possible to disable releases on a repository, in the same way it is possible to disable issues or packages.
* [Git reflog support](
The [git reflog]( are now active by default on all repositories and
kept around for 90 days. It allows the Forgejo admin to recover the previous tip of a branch after an
accidental force push.
[Read more about reflog](
* [Actions]( an experimental CI/CD
It appears for the first time in this Forgejo release but is not yet fit for production. It is not fully implemented and may be insecure. However, as long as it is not enabled, it presents no risk to existing Forgejo instances.
If a repository has a file such as `.forgejo/workflows/test.yml`, it will be interpreted, for instance to run tests and verify the code in the repository works as expected (Continuous Integration). It can also be used to create HTML pages for a website and publish them (Continous Deployment). The syntax is similar to GitHub Actions and the jobs can be controled from the Forgejo web interface.
[Read more about Forgejo Actions](
<img src="./releases/images/forgejo-v1.19.0-0-rc0.png" alt="Actions" width="600" />
* User Interface improvements
* [Review box on small screens](
The rendering of the review box is improved on small screens.
* [Video element enabled in markdown](
The `<video>` HTML tag can now be used in MarkDown, with the `src`, `autoplay`, and `controls` attributes.
* [Copy citation file content in APA and BibTex format](
If a [BibTeX]( file named `CITATION.bib` is at the root of the repository, it can be conveniently copied and converted in APA by following the `Cite this repository` link.
<img src="./releases/images/forgejo-v1.19-citation-link.png" alt="Citation link" width="500" />
It will open a dialog box with the available formats and a preview of the content.
<img src="./releases/images/forgejo-v1.19-citation-dialog.png" alt="Citation dialog" width="500" />
The CFF format is also supported when a `CITATION.cff` file used instead.
* [Display asciicast](
Files with the `.cast` extension are displayed in the Forgejo web interface as [asciicast v2]( using [asciinema-player](
* [Attention blocks Note and Warning](
For each quote block, the first `**Note**` or `**Warning**` gets an icon prepended to it and its text is colored accordingly.
<img src="./releases/images/forgejo-v1.19-note-warning.png" alt="Attention block" width="400" />
* [Support for commit cross references](
A commit hash can now be prefixed by the repository to be referenced from a comment in another repository: `owner/repo@commit`.
* [Preview images for Issue cards in Project Board view](
If the card preview in the project is set to **Images and Text**, it displays images found in the corresponding issue. The most recent is displayed first, up to five images.
[Read more about card preview images](
* [Add "Copy" button to file view of raw text](
If a raw text file is displayed, a copy button of the text is enabled.
<img src="./releases/images/forgejo-v1.19-raw-copy-before.png" alt="Raw copy before" width="500" />
<img src="./releases/images/forgejo-v1.19-raw-copy-after.png" alt="Raw copy after" width="500" />
* [Setting to allow edits on PRs by maintainers](
Add setting to allow edits by maintainers by default, to avoid having to often ask contributors to enable this.
* Container images upgraded to Alpine 3.17
The Forgejo container images are now based on [Alpine 3.17]( instead of Alpine 3.16. It includes an upgrade from git 2.36.5 to git 2.38.4 and from openssh 9.0p1 to openssh 9.1p1.
## 1.18.5-0
This stable release contains an **important security fix** for Forgejo to raise the protection against brute force attack on hashed passwords stored in the database to match industry standards, [as described in detail in a companion blog post](
### Recommended Action
We **strongly recommend** that all Forgejo installations are upgraded to the latest version as soon as possible.
If `PASSWORD_HASH_ALGO` is explicitly set in `app.ini`, comment it out so that the stronger algorithm is used instead.
All password hashes stored with another algorithm will be updated to the new algorithm on the next usage of this password (e.g. a user provides the password to the Forgejo server when they login). It does not require manual intervention.
### Forgejo
* Upgrade the default password hash algorithm to pbkdf2 with 320,000 iterations (
* Return the Forgejo semantic version instead of "development" (
### Gitea
* Provide the ability to set password hash algorithm parameters ( (
* Use `--message=%s` for git commit message ( (
* Render access log template as text instead of HTML ( (
* Fix the Manually Merged form ( (
* Use beforeCommit instead of baseCommit ( (
* Display attachments of review comment when comment content is blank ( (
* Return empty url for submodule tree entries ( (
* Notify on container image create ( (
* Some refactor about code comments( (
Note that there is no Forgejo v1.18.4-N because Gitea v1.18.4 was replaced by Gitea v1.18.5 a few days after its release because of a regression. Forgejo was not affected.
## 1.18.3-2
This stable release includes a security fix for `git` and bug fixes.
### Git
Git [recently announced]( new versions to address two CVEs ([CVE-2023-22490](, [CVE-2023-23946]( On 14 Februrary 2023, Git published the maintenance release v2.39.2, together with releases for older maintenance tracks v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. All major GNU/Linux distributions also provide updated packages via their security update channels.
We recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible.
* When using a Forgejo binary: upgrade the `git` package to a version greater or equal to v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7 or v2.30.8
* When using a Forgejo container image: `docker pull`
### Forgejo
* Use proxy for pull mirror ( (
* Revert "Fixes accessibility of empty repository commit status" (
* A regression introduced in 1.18.3-1 prevented the CI status from displaying for commits with more than one pipeline
* The tag SHA in the uploaded repository must match ( [Read more about the consequences of this on the Forgejo blog](
### Gitea
* Load issue before accessing index in merge message ( (
* Fix isAllowed of escapeStreamer ( (
* Escape filename when assemble URL ( (
* Fix PR file tree folders no longer collapsing ( (
* Fix incorrect role labels for migrated issues and comments ( (
* Fix blame view missing lines ( (
* Fix 404 error viewing the LFS file ( (
* Add command to bulk set must-change-password ( (
## 1.18.3-1
This stable release includes bug fixes.
### Forgejo
* Add ARIA support for Fomantic UI checkboxes (
* Fixes accessibility behavior of Watching, Staring and Fork buttons (
* Add main landmark to templates and adjust titles (
* Improve checkbox accessibility a bit by adding the title attribute (
* Improve accessibility of navigation bar and footer (
* Use DNS queries to figure out the latest Forgejo version (
* Change the values for the nodeinfo API to correctly identify the software as Forgejo (
* CI
* Use tagged test environment for stable branches (
### Gitea
* Fix missing message in git hook when pull requests disabled on fork ( (
* add default user visibility to cli command "admin user create" ( (
* Fix color of tertiary button on dark theme ( (
* Fix restore repo bug, clarify the problem of ForeignIndex ( (
* Escape path for the file list ( (
* Fix bugs with WebAuthn preventing sign in and registration. ( (
* Improve checkIfPRContentChanged ( (
## 1.18.3-0
This stable release includes bug fixes.
### Forgejo
* Fix line spacing for plaintext previews ( (
* Fix README TOC links ( (
* Don't return duplicated users who can create org repo ( (
* Link issue and pull requests status change in UI notifications directly to their event in the timelined view. ( (
### Gitea
* Add missing close bracket in imagediff ( (
* Fix wrong hint when deleting a branch successfully from pull request UI ( (
* Fix missing message in git hook when pull requests disabled on fork ( (
## 1.18.2-1
This stable release includes a security fix. It was possible to reveal a user's email address, which is problematic because users can choose to hide their email address from everyone. This was possible because the notification email for a repository transfer request to an organization included every user's email address in the owner team. This has been fixed by sending individual emails instead and the code was refactored to prevent it from happening again.
We **strongly recommend** that all installations are upgraded to the latest version as soon as possible.
### Gitea
* When updating by rebase we need to set the environment for head repo ( (
* Mute all links in issue timeline (
* Truncate commit summary on repo files table. ( (
* Prevent multiple `To` recipients ( (
## 1.18.2-0
This stable release includes bug fixes.
### Gitea
* Fix issue not auto-closing when it includes a reference to a branch ( (
* Fix invalid issue branch reference if not specified in template ( (
* Fix 500 error viewing pull request when fork has pull requests disabled ( (
* Reliable selection of admin user ( (
## 1.18.1-0
This is the first Forgejo stable point release.
### Forgejo
### Critical security update for Git
Git [recently announced]( new versions to address two CVEs ([CVE-2022-23521](, [CVE-2022-41903]( On 17 January 2023, Git published the maintenance release v2.39.1, together with releases for older maintenance tracks v2.38.3, v2.37.5, v2.36.4, v2.35.6, v2.34.6, v2.33.6, v2.32.5, v2.31.6, and v2.30.7. All major GNU/Linux distributions also provide updated packages via their security update channels.
We **strongly recommend** that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible.
* When using a Forgejo binary: upgrade the `git` package to a version greater or equal to v2.39.1, v2.38.3, v2.37.5, v2.36.4, v2.35.6, v2.34.6, v2.33.6, v2.32.5, v2.31.6, or v2.30.7
* When using a Forgejo container image: `docker pull`
Read more in the [Forgejo blog](
#### Release process stability
The [release process]( based on [Woodpecker CI]( was entirely reworked to be more resilient to transient errors. A new release is first uploaded into the new [Forgejo experimental]( organization for testing purposes.
Automated end to end testing of releases was implemented with a full development cycle including the creation of a new repository and a run of CI. It relieves the user and developer from the burden of tedious manual testing.
#### Container environment variables
When running a container, all environment variables starting with `FORGEJO__` can be used instead of `GITEA__`. For backward compatibility with existing scripts, it is still possible to use `GITEA__` instead of `FORGEJO__`. For instance:
docker run --name forgejo -e FORGEJO__security__INSTALL_LOCK=true
#### Forgejo hook types
A new `forgejo` hook type is available and behaves exactly the same as the existing `gitea` hook type. It will be used to implement additional features specific to Forgejo in a way that will be backward compatible with Gitea.
#### X-Forgejo headers
Wherever a `X-Gitea` header is received or sent, an identical `X-Forgejo` is added. For instance when a notification mail is sent, the `X-Forgejo-Reason` header is set to explain why. Or when a webhook is sent, the `X-Forgejo-Event` header is set with `push`, `tag`, etc. for Woodpecker CI to decide on an action.
#### Look and feel fixes
The Forgejo theme was [modified]( to take into account user feedback.
### Gitea
* Add `sync_on_commit` option for push mirrors api ( (
* Update `` (
* Fix pull request API field `closed_at` always being `null` ( (
* Fix container blob mount ( (
* Fix error when calculating repository size ( (
* Fix Operator does not exist bug on explore page with ONLY_SHOW_RELEVANT_REPOS ( (
* Fix environments for KaTeX and error reporting ( (
* Remove the netgo tag for Windows build ( (
* Fix migration from GitBucket ( (
* Prevent panic on looking at api "git" endpoints for empty repos ( (
* Fix PR status layout on mobile ( (
* Fix wechatwork webhook sends empty content in PR review ( (
* Remove duplicate "Actions" label in mobile view ( (
* Fix leaving organization bug on user settings -> orgs ( (
* Fixed colour transparency regex matching in project board sorting ( (
* Correctly handle select on multiple channels in Queues ( (
* Prepend refs/heads/ to issue template refs ( (
* Restore function to "Show more" buttons ( (
* Continue GCing other repos on error in one repo ( (
* Allow HOST has no port ( (
* Fix omit avatar_url in discord payload when empty ( (
* Don't display stop watch top bar icon when disabled and hidden when click other place ( (
* Don't lookup mail server when using sendmail ( (
* Fix gravatar disable bug (
* Fix update settings table on install ( (
* Fix sitemap ( (
* Fix code search title translation ( (
* Fix due date rendering the wrong date in issue ( (
* Fix get system setting bug when enabled redis cache (
* Fix bug of DisableGravatar default value (
* Fix key signature error page ( (
* Remove test session cache to reduce possible concurrent problem ( (
* Restore previous official review when an official review is deleted ( (
* Log STDERR of external renderer when it fails ( (
## 1.18.0-1
This is the first Forgejo release.
### Forgejo improvements
#### Woodpecker CI
A new [CI configuration]( based on [Woodpecker CI]( was created. It is used to:
* run tests on every Forgejo pull request ([compliance](, [unit tests and integration tests](
* publish the Forgejo v1.18.0-1 release, [as binary packages]( for amd64, arm64 and armv6 and [container images]( for amd64 and arm64, root and rootless
#### Look and feel
The default themes were replaced by Forgejo themes and the landing page was [modified]( to display the Forgejo logo and names but the look and feel remains otherwise identical to Gitea.
<img src="./releases/images/forgejo-v1.18.0-rc1-2-landing.jpg" alt="Landing page" width="600" />
#### Privacy
Gitea instances fetch weekly by default, which raises privacy concerns. In Forgejo [this feature needs to be explicitly activated]( at installation time or by modifying the configuration file. Forgejo also provides an alternative [RSS feed]( to be informed when a new release is published.
### Gitea
* Remove ReverseProxy authentication from the API ( (
* Support Go Vulnerability Management (
* Forbid HTML string tooltips (
* Rework mailer settings (
* Remove U2F support (
* Refactor `i18n` to `locale` (
* Enable contenthash in filename for dynamic assets (
* Add color previews in markdown (
* Allow package version sorting (
* Add support for Chocolatey/NuGet v2 API (
* Add API endpoint to get changed files of a PR (
* Add filetree on left of diff view (
* Support Issue forms and PR forms (
* Add support for Vagrant packages (
* Add support for `npm unpublish` (
* Add badge capabilities to users (
* Add issue filter for Author (
* Add KaTeX rendering to Markdown. (
* Add support for Pub packages (
* Support localized README (
* Add support mCaptcha as captcha provider (
* Add team member invite by email (
* Added email notification option to receive all own messages (
* Switch Unicode Escaping to a VSCode-like system (
* Add user/organization code search (
* Only show relevant repositories on explore page (
* User keypairs and HTTP signatures for ActivityPub federation using go-ap (
* Add sitemap support (
* Allow creation of OAuth2 applications for orgs (
* Add system setting table with cache and also add cache supports for user setting (
* Add pages to view watched repos and subscribed issues/PRs (
* Support Proxy protocol (
* Implement sync push mirror on commit (
* Allow empty assignees on pull request edit ( (
* Make external issue tracker regexp configurable via API (
* Add name field for org api (
* Show teams with no members if user is admin (
* Add latest commit's SHA to content response (
* Add allow_rebase_update, default_delete_branch_after_merge to repository api response (
* Add new endpoints for push mirrors management (
* Add setting to disable the git apply step in test patch ( (
* Multiple improvements for comment edit diff ( (
* Fix button in branch list, avoid unexpected page jump before restore branch actually done ( (
* Fix flex layout for repo list icons ( (
* Fix vertical align of committer avatar rendered by email address ( (
* Fix setting HTTP headers after write ( (
* Color and Style enhancements (, #21799) (
* Ignore line anchor links with leading zeroes ( (
* Quick fixes monaco-editor error: "vs.editor.nullLanguage" ( (
* Use CSS color-scheme instead of invert ( (
* Respect user's locale when rendering the date range in the repo activity page (
* Change `commits-table` column width (
* Refactor git command arguments and make all arguments to be safe to be used (
* CSS color enhancements (
* Add link to user profile in markdown mention only if user exists (, #21554)
* Add option to skip index dirs (
* Diff file tree tweaks (
* Localize all timestamps (
* Add `code` highlighting in issue titles (
* Use Name instead of DisplayName in LFS Lock (
* Consolidate more CSS colors into variables (
* Redirect to new repository owner (
* Use ISO date format instead of hard-coded English date format for date range in repo activity page (
* Use weighted algorithm for string matching when finding files in repo (
* Show private data in feeds (
* Refactor parseTreeEntries, speed up tree list (
* Add GET and DELETE endpoints for Docker blob uploads (
* Add nicer error handling on template compile errors (
* Add `stat` to `ToCommit` function for speed (
* Support instance-wide OAuth2 applications (
* Record OAuth client type at registration (
* Add new CSS variables --color-accent and --color-small-accent (
* Improve error descriptions for unauthorized_client (
* Case-insensitive "find files in repo" (
* Consolidate more CSS rules, fix inline code on arc-green (
* Log real ip of requests from ssh (
* Save files in local storage as group readable (
* Enable fluid page layout on medium size viewports (
* File header tweaks (
* Added missing headers on user packages page (
* Display image digest for container packages (
* Skip dirty check for team forms (
* Keep path when creating a new branch (
* Remove fomantic image module (
* Make labels clickable in the comments section. (
* Sort branches and tags by date descending (
* Better repo API unit checks (
* Improve commit status icons (
* Limit length of repo description and repo url input fields (
* Show .editorconfig errors in frontend (
* Allow poster to choose reviewers (
* Remove black labels and CSS cleanup (
* Make e-mail sanity check more precise (
* Use native inputs in whitespace dropdown (
* Enhance package date display (
* Display total blob size of a package version (
* Show language name on hover (
* Show instructions for all generic package files (
* Refactor AssertExistsAndLoadBean to use generics (
* Move the official website link at the footer of gitea (
* Add support for full name in reverse proxy auth (
* Remove useless JS operation for relative time tooltips (
* Replace some icons with SVG (
* Change commit status icons to SVG (
* Improve single repo action for issue and pull requests (
* Allow multiple files in generic packages (
* Add option to create new issue from /issues page (
* Background color of private list-items updated (
* Added search input field to issue filter (
* Increase default item listing size `ISSUE_PAGING_NUM` to 20 (
* Modify milestone search keywords to be case insensitive again (
* Show hint to link package to repo when viewing empty repo package list (
* Add Tar ZSTD support (
* Make code review checkboxes clickable (
* Add "X-Gitea-Object-Type" header for GET `/raw/` & `/media/` API (
* Display project in issue list (
* Prepend commit message to template content when opening a new PR (
* Replace fomantic popup module with tippy.js (
* Allow to specify colors for text in markup (
* Allow access to the Public Organization Member lists with minimal permissions (
* Use default values when provided values are empty (
* Vertical align navbar avatar at middle (
* Delete cancel button in repo creation page (
* Include login_name in adminCreateUser response (
* fix: icon margin in user/settings/repos (
* Remove blue text on migrate page (
* Modify milestone search keywords to be case insensitive (
* Move some files into models' sub packages (
* Add tooltip to repo icons in explore page (
* Remove deprecated licenses (
* Webhook for Wiki changes (
* Share HTML template renderers and create a watcher framework (
* Allow enable LDAP source and disable user sync via CLI (
* Adds a checkbox to select all issues/PRs (
* Refactor `i18n` to `locale` (
* Disable status checks in template if none found (
* Allow manager logging to set SQL (
* Add order by for assignee no sort issue (
* Take a stab at porting existing components to Vue3 (
* Add doctor command to write commit-graphs (
* Add support for authentication based on reverse proxy email (
* Enable spellcheck for EasyMDE, use contenteditable mode (
* Allow specifying SECRET_KEY_URI, similar to INTERNAL_TOKEN_URI (
* Rework mailer settings (
* Add option to purge users (
* Add author search input (
* Make rss/atom identifier globally unique (
* Auth interface return error when verify failure ( (
* Use complete SHA to create and query commit status ( (
* Update bleve and zapx to fix unaligned atomic ( (
* Prevent panic in doctor command when running default checks ( (
* Load GitRepo in API before deleting issue ( (
* Ignore line anchor links with leading zeroes ( (
* Set last login when activating account ( (
* Fix UI language switching bug ( (
* Quick fixes monaco-editor error: "vs.editor.nullLanguage" ( (
* Allow local package identifiers for PyPI packages ( (
* Deal with markdown template without metadata ( (
* Fix opaque background on mermaid diagrams ( (
* Fix repository adoption on Windows ( (
* Sync git hooks when config file path changed ( (
* Fix 500 on PR files API ( (
* Fix `Timestamp.IsZero` ( (
* Fix viewing user subscriptions (
* Fix mermaid-related bugs (
* Fix branch dropdown shifting on page load (
* Fix default theme-auto selector when nologin (
* Fix and improve incorrect error messages (
* Fix formatted link for PR review notifications to matrix (
* Center-aligning content of WebAuthN page (
* Remove follow from commits by file (
* Fix commit status popup (
* Fix init mail render logic (
* Use correct page size for link header pagination (
* Preserve unix socket file (
* Use tippy.js for context popup (
* Add missing parameter for error in log message (
* Do not allow organisation owners add themselves as collaborator (
* Rework file highlight rendering and fix yaml copy-paste (
* Improve code diff highlight, fix incorrect rendered diff result (
* Improve OAuth integration tests (
* Add playwright tests (
* Switch to building with go1.19 (
* Update JS dependencies, adjust eslint (
* Add more linters to improve code readability (
## 1.18.0-0
This release was replaced by 1.18.0-1 a few hours after being published because the release process [was interrupted](
## 1.18.0-rc1-2
This is the first Forgejo release candidate.