forgejo/RELEASE-NOTES.md

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.3-0

The complete list of commits included in the Forgejo v1.21.3-0 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.21.2-1..v1.21.3-0

This stable release includes bug fixes. It was built with an updated version of the Go Cryptography package that fixes CVE-2023-48795. As explained in the corresponding Go issue: "The impact of this attack is relatively limited, as it does not compromise confidentiality of the channel."

• Recommended Action

  We recommend that all Forgejo installations are upgraded to the latest version.

• Forgejo Semantic Version

  The semantic version was updated to 6.0.3+0-gitea-1.21.3

• Security fix

  • The Go Cryptography package is upgraded to fix CVE-2023-48795.

• 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 a regression in how the markdown anchors are generated. For instance the anchor for A.B.C is A-B-C but was incorrectly set to ABC.
  • Fix the branch name of scheduled actions which was sometime incorrectly set.
  • Fix a visual glitch when setting an emoji in the web UI.
  • Recently Docker started to use the optional POST /v2/token endpoint which should respond with a 404 Not Found status code instead of the current 405 Method Not Allowed.
  • Fix a missing leading ssh:// when using a port other than 22 when Git URLs are displayed in the web UI.
  • Allow disabling the detection of ambiguous unicode characters with the new setting AMBIGUOUS_UNICODE_DETECTION=false.
  • Fix a regression with the issue references rendering in wiki pages.
  • Fix merging artifact chunks error when minio storage basepath is set
  • Fix missing information in the blame page web UI.

1.21.2-1

The complete list of commits included in the Forgejo v1.21.2-1 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.21.2-0..v1.21.2-1

This stable release contains a security fix, as explained in the v1.21.2-1 companion blog post.

• 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 to 6.0.2+0-gitea-1.21.2

• Security fix

  The project page of private users is no longer publicly visible.

• 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.

  • The default preferred licenses for the [repository].PREFERRED_LICENSES setting were incorrect and have been fixed to be Apache-2.0 and MIT.
  • A failed cron job can no longer cause the Forgejo instance to shutdown.
  • A pull request merged by a workflow using the automatic token with the auto merge flag no longer cause an error 500 when displaying the pull request page.
  • Tentative fix for when the database branch cache is out of sync with the branches found in Git repositories. When in doubt it is recommended to click on Sync missed branches from git data to databases in the /admin dashboard.

1.21.2-0

The complete list of commits included in the Forgejo v1.21.2-0 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.21.1-0..v1.21.2-0

This stable release includes bug fixes. It was built with Go v1.21.5 that fixes CVE-2023-39326 which a malicious HTTP client can exploit to cause a server to automatically read a large amount of data. It allows for memory exhaustion in the situation that HTTP chuncked encoding requests can reach Forgejo.

• Recommended Action

  We recommend that all Forgejo installations are upgraded to the latest version.

• Forgejo Semantic Version

  The semantic version was updated to 6.0.1+0-gitea-1.21.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.

  • OAuth2 uses the link_account page when the email or username is missing
  • Avoid conflicts of issue and PR numbers in GitLab migration
  • Only pass selected repository IDs to pagination
  • Add download URL for executable files
  • Fix Forgejo repositories migration to also include issues, prs etc.
  • Fix template substitution bug preventing notifications to be sent on new user registration
  • When searching for issues, require that all terms are matched instead of one of them
  • Ignore temporary files when calculating the size of a repository
  • Convert git commit summary to valid UTF8
  • Fix incorrect default value of [attachment].MAX_SIZE
  • Fix object does not exist error when checking citation file

• Improvements

  • new doctor check: fix-push-mirrors-without-git-remote
  • Add HEAD support for RPM registry

1.21.1-0

The complete list of commits included in the Forgejo v1.21.1-0 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ 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). A Q&A discussion is available to share tips and tricks. A new section was also added to the developer documentation about interface customization.

  • If you have custom asset files, e.g. custom themes, inside custom/public/* (css included), you need to transfer these files to custom/public/assets/* for them to be detected. Read more in the documentation and the Q&A discussion dedicated to interface customization.
  • Git branches are stored in the databases to reduce the calls to a git process and improve performances. After upgrading, login as an admin, go to the /admin page and click run Sync missed branches from git data to databases. If this is not done there will be messages such as LoadBranches: branch does not exist in the logs.
  • 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. Existing MySQL databases still using utf8 can be converted using the CLI: forgejo doctor convert.
  • 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.
  • 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.
  • The minimum RSA keylength is now 3072 instead of 2048.
  • Prior to this release, a token scoped to read or write permissions on issues was allowed to access both issues and pull requests, regardless of the restrictions imposed to the team in which they belong. In a team it is possible to grant finer grained permissions, for instance to allow a user to access issues but not pull requests. These restrictions are now enforced and API calls that previously succeeded on /api/v1/repos/{org}/{repo}/issues or other endpoints common to both issues and pull requests could return 404. Granting the user the necessary permissions in the team in which they belong will allow them to use that endpoint again.

• Forgejo Actions: It is now enabled by default but should still be considered alpha stage and subject to unannounced breaking changes.

  • The API can now be used to manage secrets for users, organizations and repositories.
  • Registration tokens can register multiple runners instead of a single one. Read more about runner registration.
  • Add support for variables in addition to secrets.
  • Add support for recurring actions similar to cron jobs.
  • Add the possibility to disable workflows from the user interface.
  • Add automatic cleanup of artificats.
  • Add automatic cancelation of jobs when pushing new commits to a PR.
  • Add support for uploading multiple artificats.
  • Add support for the pull_request_target event which has access to secrets because it runs using the workflows from the base branch instead of the pull request.
  • Add support for reading labels from the runner instead of specifying them during registration.

• Features:

  • With the Chroma upgrade from 2.7.0 to 2.10.0 syntax highlighting is now available for Smali, DHCP, WebGPU Shading Language, AutoHotkey, AutoIt, tal (uxntal), ArangoDB Query Language (AQL), BIND DNS Zone, Odin, Sourcepawn, CPP, C. New files and extensions are associated as follows: .tpp as a c++, .eex as a Elixir, Pipfile and poetry.lock as a TOML, ISCdhcpd filename, .twig, Mathematica.
  • With the go-enry upgrade from v2.8.4 to v2.8.6, language detection in the repository now includes:
    • Bluespec BH: atom-haskell/language-haskell
    • D2: terrastruct/d2-vscode
    • Go Workspace: golang/vscode-go
    • Gradle Kotlin DSL: nishtahir/language-kotlin
    • Hosts File: Alhadis/language-etc
    • LOLCODE: KrazIvan/LOLCODE-grammar-vscode
    • MDX: wooorm/markdown-tm-language
    • Nasal: BobDotCom/Nasal.tmbundle
    • Nushell: hustcer/nu-grammar
    • Pact: kadena-io/pact-atom
    • RBS: soutaro/vscode-rbs-syntax
    • Rez: textmate/rez.tmbundle
    • Sweave: textmate/sweave.tmbundle
    • TL-Verilog: adamint/tlv-vscode
    • Typst: michidk/typst-grammar
    • WDL: broadinstitute/wdl-sublime-syntax-highlighter
    • WGSL: wgsl-analyzer/wgsl-analyzer
    • WebAssembly Interface Type: bytecodealliance/vscode-wit
  • Newly pushed branches show in the web UI with a link to create a PR. Read more about the New Pull Request button.
  • Labels that are no longer useful can be archived. They can no longer be selected but they remain on existing issues. Read more about archiving labels.
  • The blame view now takes into account the .git-blame-ignore-revs file.
  • Pre-register OAuth2 applications for git credential helpers. Read more in the git authentication section of the user guide and the administrator guide.
  • Admins can be notified via email when a new user registers to help fight spam bots by setting [admin].SEND_NOTIFICATION_EMAIL_ON_NEW_USER = true.
  • When a page display the history of changes for a file, file rename are detected and displayed.
  • Packages can be configured to redirect requests to the S3 server for clients that support this feature.
  • When a PR contains multiple commits, it is now possible review to each commit independently. Read more about selecting commits for review.
  • Issues can be deleted in batch.
  • An email can be associated with an Organisations.
  • The CODEOWNERS file is interpreted to automatically set reviewers on PRs. The CODEOWNERS file is loaded from these paths in this order: ./CODEOWNERS, ./docs/CODEOWNERS.
  • Issue search were reworked entirely to fix the shortcomings of the previous implementation.
  • Allow "latest" to be used as a release tag when downloading a file.
  • Authentication via reverse proxy is available and disabled by default.
  • Add API for changing avatars.

• User Interface:

  • Show OpenID Connect and OAuth on the signup page.
  • Show branches and tags that contain the commit being displayed
  • Add 'Show on a map' button to the location in the usr profile.
  • Render plaintext task list items for markdown files.
  • The administrators user details page was modified.
  • When mirroring a repository fails, a Retry button allows to re-create it.
  • Package cleanup can be triggered from from administration web interface.
  • In the page displaying the list of branches, it is now possible to search them by name.
  • Display all user types (including bots) org types on the administration web interface.
  • Improve opengraph previews.
  • Render code blocks in the repository description.
  • Add member, collaborator, contributor, and first-time contributor roles and tooltips next to the author.
  • It is no longer possible to change the run user in the installation page.
  • Update emoji set to Unicode 15.
  • Improve the image diff user interface.
  • Allow rebuilding the issue index from the cron task list in the admin panel.

• Enhancements:

  • Improve the privacy of the user profile settings.
  • Add the upload URL to the release API.
  • Allow editing existing push mirrors from the settings page of a repository.
  • Add a link to the OpenID issuer URL in the WebFinger response.
  • Support copy protected branches with template repositories.
  • In the administration web interface, split the lfs size from repository size.

• Bug fixes:

  • Allow empty Conan files.
  • Fix the incorrect route path in the user edit page. .
  • Add auth-required to config.json for Cargo sparse registry.
  • Rewrite the DiffFileTreeItem and fix misalignment .
  • Do not "guess" the file encoding/BOM when using API to upload files.

• Security:

  • Do not show the profile README when a repository is private.
  • A security.txt files is provided by default and other static files can also be added.

1.20.6-1

The complete list of commits included in the Forgejo v1.20.6-1 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.20.6-0..v1.20.6-1

This stable release contains a security fix.

• 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 to 5.0.8+0-gitea-1.20.6

• Security fix

  The project page of private users is no longer publicly visible.

• Bug fix

  • Consider executable files as a valid case when returning a downloadURL for them. They are just regular files with the difference being the executable permission bit being set.

• New doctor check and fix

  • Adds a new doctor check: fix-push-mirrors-without-git-remote. The new check looks for push mirrors that do not have their remotes configured in git. If automatic fixing is enabled, it will remove these push mirrors from the database.

1.20.6-0

The complete list of commits included in the Forgejo v1.20.6-0 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.20.5-1..v1.20.6-0

This stable release contains a security fix, as explained in the v1.20.6-0 companion blog post.

• 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 to 5.0.7+0-gitea-1.20.6

• Breaking change

  Prior to this release, a token scoped to read or write permissions on issues was allowed to access both issues and pull requests, regardless of the restrictions imposed to the team in which they belong. In a team it is possible to grant finer grained permissions, for instance to allow a user to access issues but not pull requests. These restrictions are now enforced and API calls that previously succeeded on /api/v1/repos/{org}/{repo}/issues or other endpoints common to both issues and pull requests could return 404. Granting the user the necessary permissions in the team in which they belong will allow them to use that endpoint again.

• Security fix

  Additional API and web endpoints now fail when given manually crafted identifiers.

1.20.5-1

The complete list of commits included in the Forgejo v1.20.5-1 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.20.5-0..v1.20.5-1

This stable release contains critical security fixes, as explained in the v1.20.5-1 companion blog post.

• 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 to 5.0.6+0-gitea-1.20.5

• Security fixes

  • API and web endpoints now fail when given manually crafted identifiers.
  • When an extension is added to the URL of a user profile (e.g. /myuser.rss) it is now verified to be visible.
  • docker login now fails with basic auth when 2FA is enabled.

• Bug fixes

  The most prominent bug fixes are described below. Others can be found in the list of commits included in the release as described above.

  • Create the ActionTaskOutput table for new Forgejo instances.
  • Restricted users only see repos in orgs which their team was assigned to.
  • Release assets are now taken into account during a migration from GitLab, Forgejo or Gitea.
  • When webhook.PROXY_URL is set, the ALLOWED_HOST_LIST setting is now properly enforced.
  • It is now possible to access /<username>/<reponame>/attachments/<uuid> with an application token and the attachments API download URL is usable.

1.20.5-0

The complete list of commits included in the Forgejo v1.20.5-0 release can be reviewed from the command line with:

$ git clone https://codeberg.org/forgejo/forgejo/
$ git -C forgejo log --oneline --no-merges v1.20.4-1..v1.20.5-0

This stable release contains an important security fix, as explained in the v1.20.5-0 companion blog post.

• 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 to 5.0.5+0-gitea-1.20.5

• Security fix

  • When a user logs into Forgejo, they can click the Remember This Device checkbox and their browser will store a Long-term authentication token provided by the server, in a cookie that will allow them to stay logged in for an extended period of time. The implementation was inherently insecure and was reworked. Read more about this issue in the v1.20.5-0 blog post.

• Bug fixes

  The most prominent bug fixes are described below. Others can be found in the list of commits included in the release as described above.

  • Fix the display of pull requests waiting for review on the /pulls page. It incorrectly included all reviews.
  • Fix a v1.20 regression preventing access to files with OAuth2 tokens in private repositories.
  • Fix a bug by which the doctor command complains the deleted_branch table is missing although it should not.
  • Fix the release URL in webhooks so that URL points to the API URL and HTMLURL points to the web page.
  • Fix organization field being null in POST /orgs/{orgid}/teams.

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 https://codeberg.org/forgejo/forgejo/
$ 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 https://codeberg.org/forgejo/forgejo/
$ 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 https://codeberg.org/forgejo/forgejo/
$ 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 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 https://codeberg.org/forgejo/forgejo/
$ 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 email-setup.en-us.md
  • 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 https://codeberg.org/forgejo/forgejo/
$ 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 README.md file of the .profile repository, if it exists. It is a breaking change because it will display the .profile/README.md 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) 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 https://codeberg.org/forgejo/forgejo/
$ 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 https://codeberg.org/forgejo/forgejo/
$ 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 https://codeberg.org/forgejo/forgejo/
$ 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 https://codeberg.org/forgejo/forgejo/
$ 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 user.name. Because of a bug in Chi it was not possible to access /user.name.png, /user.name.gpg, 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 docker.io/library/golang:1.20-alpine3.17 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 https://codeberg.org/forgejo/forgejo/
$ 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 https://codeberg.org/forgejo/forgejo/
$ 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.

    

  • 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. http://www.openssh.com/legacy.html

  • 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.

    

    ...

    

    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

    

• 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.

    

    It will open a dialog box with the available formats and a preview of the content.

    

    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.

    

  • 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.

    Before

    

    After

    

  • 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

• SECURITY
  • Upgrade the default password hash algorithm to pbkdf2 with 320,000 iterations (https://codeberg.org/forgejo/forgejo/pulls/407)
• BUGFIXES
  • Return the Forgejo semantic version instead of "development" (https://codeberg.org/forgejo/forgejo/pulls/381)

Gitea

• SECURITY
  • Provide the ability to set password hash algorithm parameters (https://github.com/go-gitea/gitea/pull/22942) (https://github.com/go-gitea/gitea/pull/22943)
• BUGFIXES
  • Use --message=%s for git commit message (https://github.com/go-gitea/gitea/pull/23028) (https://github.com/go-gitea/gitea/pull/23029)
  • Render access log template as text instead of HTML (https://github.com/go-gitea/gitea/pull/23013) (https://github.com/go-gitea/gitea/pull/23025)
  • Fix the Manually Merged form (https://github.com/go-gitea/gitea/pull/23015) (https://github.com/go-gitea/gitea/pull/23017)
  • Use beforeCommit instead of baseCommit (https://github.com/go-gitea/gitea/pull/22949) (https://github.com/go-gitea/gitea/pull/22996)
  • Display attachments of review comment when comment content is blank (https://github.com/go-gitea/gitea/pull/23035) (https://github.com/go-gitea/gitea/pull/23046)
  • Return empty url for submodule tree entries (https://github.com/go-gitea/gitea/pull/23043) (https://github.com/go-gitea/gitea/pull/23048)
  • Notify on container image create (https://github.com/go-gitea/gitea/pull/22806) (https://github.com/go-gitea/gitea/pull/22965)
  • Some refactor about code comments(https://github.com/go-gitea/gitea/pull/20821) (https://github.com/go-gitea/gitea/pull/22707)

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 codeberg.org/forgejo/forgejo:1.18.3-2

Forgejo

• BUGFIXES
  • Use proxy for pull mirror (https://github.com/go-gitea/gitea/pull/22771) (https://github.com/go-gitea/gitea/pull/22772)
  • Revert "Fixes accessibility of empty repository commit status" (https://github.com/go-gitea/gitea/pull/22632)
    • A regression introduced in 1.18.3-1 prevented the CI status from displaying for commits with more than one pipeline
• FORGEJO RELEASE PROCESS BUGFIXES
  • The tag SHA in the uploaded repository must match (https://codeberg.org/forgejo/forgejo/pulls/345) Read more about the consequences of this on the Forgejo blog

Gitea

• BUGFIXES
  • Load issue before accessing index in merge message (https://github.com/go-gitea/gitea/pull/22822) (https://github.com/go-gitea/gitea/pull/22830)
  • Fix isAllowed of escapeStreamer (https://github.com/go-gitea/gitea/pull/22814) (https://github.com/go-gitea/gitea/pull/22837)
  • Escape filename when assemble URL (https://github.com/go-gitea/gitea/pull/22850) (https://github.com/go-gitea/gitea/pull/22871)
  • Fix PR file tree folders no longer collapsing (https://github.com/go-gitea/gitea/pull/22864) (https://github.com/go-gitea/gitea/pull/22872)
  • Fix incorrect role labels for migrated issues and comments (https://github.com/go-gitea/gitea/pull/22914) (https://github.com/go-gitea/gitea/pull/22923)
  • Fix blame view missing lines (https://github.com/go-gitea/gitea/pull/22826) (https://github.com/go-gitea/gitea/pull/22929)
  • Fix 404 error viewing the LFS file (https://github.com/go-gitea/gitea/pull/22945) (https://github.com/go-gitea/gitea/pull/22948)
• FEATURES
  • Add command to bulk set must-change-password (https://github.com/go-gitea/gitea/pull/22823) (https://github.com/go-gitea/gitea/pull/22928)

1.18.3-1

This stable release includes bug fixes.

Forgejo

• ACCESSIBILITY
  • Add ARIA support for Fomantic UI checkboxes (https://github.com/go-gitea/gitea/pull/22599)
  • Fixes accessibility behavior of Watching, Staring and Fork buttons (https://github.com/go-gitea/gitea/pull/22634)
  • Add main landmark to templates and adjust titles (https://github.com/go-gitea/gitea/pull/22670)
  • Improve checkbox accessibility a bit by adding the title attribute (https://github.com/go-gitea/gitea/pull/22593)
  • Improve accessibility of navigation bar and footer (https://github.com/go-gitea/gitea/pull/22635)
• PRIVACY
  • Use DNS queries to figure out the latest Forgejo version (https://codeberg.org/forgejo/forgejo/pulls/278)
• BRANDING
  • Change the values for the nodeinfo API to correctly identify the software as Forgejo (https://codeberg.org/forgejo/forgejo/pulls/313)
• CI
  • Use tagged test environment for stable branches (https://codeberg.org/forgejo/forgejo/pulls/318)

Gitea

• BUGFIXES
  • Fix missing message in git hook when pull requests disabled on fork (https://github.com/go-gitea/gitea/pull/22625) (https://github.com/go-gitea/gitea/pull/22658)
  • add default user visibility to cli command "admin user create" (https://github.com/go-gitea/gitea/pull/22750) (https://github.com/go-gitea/gitea/pull/22760)
  • Fix color of tertiary button on dark theme (https://github.com/go-gitea/gitea/pull/22739) (https://github.com/go-gitea/gitea/pull/22744)
  • Fix restore repo bug, clarify the problem of ForeignIndex (https://github.com/go-gitea/gitea/pull/22776) (https://github.com/go-gitea/gitea/pull/22794)
  • Escape path for the file list (https://github.com/go-gitea/gitea/pull/22741) (https://github.com/go-gitea/gitea/pull/22757)
  • Fix bugs with WebAuthn preventing sign in and registration. (https://github.com/go-gitea/gitea/pull/22651) (https://github.com/go-gitea/gitea/pull/22721)
• PERFORMANCES
  • Improve checkIfPRContentChanged (https://github.com/go-gitea/gitea/pull/22611) (https://github.com/go-gitea/gitea/pull/22644)

1.18.3-0

This stable release includes bug fixes.

Forgejo

• BUGFIXES
  • Fix line spacing for plaintext previews (https://github.com/go-gitea/gitea/pull/22699) (https://github.com/go-gitea/gitea/pull/22701)
  • Fix README TOC links (https://github.com/go-gitea/gitea/pull/22577) (https://github.com/go-gitea/gitea/pull/22677)
  • Don't return duplicated users who can create org repo (https://github.com/go-gitea/gitea/pull/22560) (https://github.com/go-gitea/gitea/pull/22562)
  • Link issue and pull requests status change in UI notifications directly to their event in the timelined view. (https://github.com/go-gitea/gitea/pull/22627) (https://github.com/go-gitea/gitea/pull/22642)

Gitea

• BUGFIXES
  • Add missing close bracket in imagediff (https://github.com/go-gitea/gitea/pull/22710) (https://github.com/go-gitea/gitea/pull/22712)
  • Fix wrong hint when deleting a branch successfully from pull request UI (https://github.com/go-gitea/gitea/pull/22673) (https://github.com/go-gitea/gitea/pull/22698)
  • Fix missing message in git hook when pull requests disabled on fork (https://github.com/go-gitea/gitea/pull/22625) (https://github.com/go-gitea/gitea/pull/22658)

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

• BUGFIXES
  • When updating by rebase we need to set the environment for head repo (https://github.com/go-gitea/gitea/pull/22535) (https://github.com/go-gitea/gitea/pull/22536)
  • Mute all links in issue timeline (https://github.com/go-gitea/gitea/pull/22534)
  • Truncate commit summary on repo files table. (https://github.com/go-gitea/gitea/pull/22551) (https://github.com/go-gitea/gitea/pull/22552)
  • Prevent multiple To recipients (https://github.com/go-gitea/gitea/pull/22566) (https://github.com/go-gitea/gitea/pull/22569)

1.18.2-0

This stable release includes bug fixes.

Gitea

• BUGFIXES
  • Fix issue not auto-closing when it includes a reference to a branch (https://github.com/go-gitea/gitea/pull/22514) (https://github.com/go-gitea/gitea/pull/22521)
  • Fix invalid issue branch reference if not specified in template (https://github.com/go-gitea/gitea/pull/22513) (https://github.com/go-gitea/gitea/pull/22520)
  • Fix 500 error viewing pull request when fork has pull requests disabled (https://github.com/go-gitea/gitea/pull/22512) (https://github.com/go-gitea/gitea/pull/22515)
  • Reliable selection of admin user (https://github.com/go-gitea/gitea/pull/22509) (https://github.com/go-gitea/gitea/pull/22511)

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 codeberg.org/forgejo/forgejo:1.18.1-0

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 codeberg.org/forgejo/forgejo:1.18.1-0

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

• API
  • Add sync_on_commit option for push mirrors api (https://github.com/go-gitea/gitea/pull/22271) (https://github.com/go-gitea/gitea/pull/22292)
• BUGFIXES
  • Update github.com/zeripath/zapx/v15 (https://github.com/go-gitea/gitea/pull/22485)
  • Fix pull request API field closed_at always being null (https://github.com/go-gitea/gitea/pull/22482) (https://github.com/go-gitea/gitea/pull/22483)
  • Fix container blob mount (https://github.com/go-gitea/gitea/pull/22226) (https://github.com/go-gitea/gitea/pull/22476)
  • Fix error when calculating repository size (https://github.com/go-gitea/gitea/pull/22392) (https://github.com/go-gitea/gitea/pull/22474)
  • Fix Operator does not exist bug on explore page with ONLY_SHOW_RELEVANT_REPOS (https://github.com/go-gitea/gitea/pull/22454) (https://github.com/go-gitea/gitea/pull/22472)
  • Fix environments for KaTeX and error reporting (https://github.com/go-gitea/gitea/pull/22453) (https://github.com/go-gitea/gitea/pull/22473)
  • Remove the netgo tag for Windows build (https://github.com/go-gitea/gitea/pull/22467) (https://github.com/go-gitea/gitea/pull/22468)
  • Fix migration from GitBucket (https://github.com/go-gitea/gitea/pull/22477) (https://github.com/go-gitea/gitea/pull/22465)
  • Prevent panic on looking at api "git" endpoints for empty repos (https://github.com/go-gitea/gitea/pull/22457) (https://github.com/go-gitea/gitea/pull/22458)
  • Fix PR status layout on mobile (https://github.com/go-gitea/gitea/pull/21547) (https://github.com/go-gitea/gitea/pull/22441)
  • Fix wechatwork webhook sends empty content in PR review (https://github.com/go-gitea/gitea/pull/21762) (https://github.com/go-gitea/gitea/pull/22440)
  • Remove duplicate "Actions" label in mobile view (https://github.com/go-gitea/gitea/pull/21974) (https://github.com/go-gitea/gitea/pull/22439)
  • Fix leaving organization bug on user settings -> orgs (https://github.com/go-gitea/gitea/pull/21983) (https://github.com/go-gitea/gitea/pull/22438)
  • Fixed colour transparency regex matching in project board sorting (https://github.com/go-gitea/gitea/pull/22092) (https://github.com/go-gitea/gitea/pull/22437)
  • Correctly handle select on multiple channels in Queues (https://github.com/go-gitea/gitea/pull/22146) (https://github.com/go-gitea/gitea/pull/22428)
  • Prepend refs/heads/ to issue template refs (https://github.com/go-gitea/gitea/pull/20461) (https://github.com/go-gitea/gitea/pull/22427)
  • Restore function to "Show more" buttons (https://github.com/go-gitea/gitea/pull/22399) (https://github.com/go-gitea/gitea/pull/22426)
  • Continue GCing other repos on error in one repo (https://github.com/go-gitea/gitea/pull/22422) (https://github.com/go-gitea/gitea/pull/22425)
  • Allow HOST has no port (https://github.com/go-gitea/gitea/pull/22280) (https://github.com/go-gitea/gitea/pull/22409)
  • Fix omit avatar_url in discord payload when empty (https://github.com/go-gitea/gitea/pull/22393) (https://github.com/go-gitea/gitea/pull/22394)
  • Don't display stop watch top bar icon when disabled and hidden when click other place (https://github.com/go-gitea/gitea/pull/22374) (https://github.com/go-gitea/gitea/pull/22387)
  • Don't lookup mail server when using sendmail (https://github.com/go-gitea/gitea/pull/22300) (https://github.com/go-gitea/gitea/pull/22383)
  • Fix gravatar disable bug (https://github.com/go-gitea/gitea/pull/22337)
  • Fix update settings table on install (https://github.com/go-gitea/gitea/pull/22326) (https://github.com/go-gitea/gitea/pull/22327)
  • Fix sitemap (https://github.com/go-gitea/gitea/pull/22272) (https://github.com/go-gitea/gitea/pull/22320)
  • Fix code search title translation (https://github.com/go-gitea/gitea/pull/22285) (https://github.com/go-gitea/gitea/pull/22316)
  • Fix due date rendering the wrong date in issue (https://github.com/go-gitea/gitea/pull/22302) (https://github.com/go-gitea/gitea/pull/22306)
  • Fix get system setting bug when enabled redis cache (https://github.com/go-gitea/gitea/pull/22298)
  • Fix bug of DisableGravatar default value (https://github.com/go-gitea/gitea/pull/22297)
  • Fix key signature error page (https://github.com/go-gitea/gitea/pull/22229) (https://github.com/go-gitea/gitea/pull/22230)
• TESTING
  • Remove test session cache to reduce possible concurrent problem (https://github.com/go-gitea/gitea/pull/22199) (https://github.com/go-gitea/gitea/pull/22429)
• MISC
  • Restore previous official review when an official review is deleted (https://github.com/go-gitea/gitea/pull/22449) (https://github.com/go-gitea/gitea/pull/22460)
  • Log STDERR of external renderer when it fails (https://github.com/go-gitea/gitea/pull/22442) (https://github.com/go-gitea/gitea/pull/22444)

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.

Privacy

Gitea instances fetch https://dl.gitea.io/gitea/version.json 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

• SECURITY
  • Remove ReverseProxy authentication from the API (https://github.com/go-gitea/gitea/pull/22219) (https://github.com/go-gitea/gitea/pull/22251)
  • Support Go Vulnerability Management (https://github.com/go-gitea/gitea/pull/21139)
  • Forbid HTML string tooltips (https://github.com/go-gitea/gitea/pull/20935)
• BREAKING
  • Rework mailer settings (https://github.com/go-gitea/gitea/pull/18982)
  • Remove U2F support (https://github.com/go-gitea/gitea/pull/20141)
  • Refactor i18n to locale (https://github.com/go-gitea/gitea/pull/20153)
  • Enable contenthash in filename for dynamic assets (https://github.com/go-gitea/gitea/pull/20813)
• FEATURES
  • Add color previews in markdown (https://github.com/go-gitea/gitea/pull/21474)
  • Allow package version sorting (https://github.com/go-gitea/gitea/pull/21453)
  • Add support for Chocolatey/NuGet v2 API (https://github.com/go-gitea/gitea/pull/21393)
  • Add API endpoint to get changed files of a PR (https://github.com/go-gitea/gitea/pull/21177)
  • Add filetree on left of diff view (https://github.com/go-gitea/gitea/pull/21012)
  • Support Issue forms and PR forms (https://github.com/go-gitea/gitea/pull/20987)
  • Add support for Vagrant packages (https://github.com/go-gitea/gitea/pull/20930)
  • Add support for npm unpublish (https://github.com/go-gitea/gitea/pull/20688)
  • Add badge capabilities to users (https://github.com/go-gitea/gitea/pull/20607)
  • Add issue filter for Author (https://github.com/go-gitea/gitea/pull/20578)
  • Add KaTeX rendering to Markdown. (https://github.com/go-gitea/gitea/pull/20571)
  • Add support for Pub packages (https://github.com/go-gitea/gitea/pull/20560)
  • Support localized README (https://github.com/go-gitea/gitea/pull/20508)
  • Add support mCaptcha as captcha provider (https://github.com/go-gitea/gitea/pull/20458)
  • Add team member invite by email (https://github.com/go-gitea/gitea/pull/20307)
  • Added email notification option to receive all own messages (https://github.com/go-gitea/gitea/pull/20179)
  • Switch Unicode Escaping to a VSCode-like system (https://github.com/go-gitea/gitea/pull/19990)
  • Add user/organization code search (https://github.com/go-gitea/gitea/pull/19977)
  • Only show relevant repositories on explore page (https://github.com/go-gitea/gitea/pull/19361)
  • User keypairs and HTTP signatures for ActivityPub federation using go-ap (https://github.com/go-gitea/gitea/pull/19133)
  • Add sitemap support (https://github.com/go-gitea/gitea/pull/18407)
  • Allow creation of OAuth2 applications for orgs (https://github.com/go-gitea/gitea/pull/18084)
  • Add system setting table with cache and also add cache supports for user setting (https://github.com/go-gitea/gitea/pull/18058)
  • Add pages to view watched repos and subscribed issues/PRs (https://github.com/go-gitea/gitea/pull/17156)
  • Support Proxy protocol (https://github.com/go-gitea/gitea/pull/12527)
  • Implement sync push mirror on commit (https://github.com/go-gitea/gitea/pull/19411)
• API
  • Allow empty assignees on pull request edit (https://github.com/go-gitea/gitea/pull/22150) (https://github.com/go-gitea/gitea/pull/22214)
  • Make external issue tracker regexp configurable via API (https://github.com/go-gitea/gitea/pull/21338)
  • Add name field for org api (https://github.com/go-gitea/gitea/pull/21270)
  • Show teams with no members if user is admin (https://github.com/go-gitea/gitea/pull/21204)
  • Add latest commit's SHA to content response (https://github.com/go-gitea/gitea/pull/20398)
  • Add allow_rebase_update, default_delete_branch_after_merge to repository api response (https://github.com/go-gitea/gitea/pull/20079)
  • Add new endpoints for push mirrors management (https://github.com/go-gitea/gitea/pull/19841)
• ENHANCEMENTS
  • Add setting to disable the git apply step in test patch (https://github.com/go-gitea/gitea/pull/22130) (https://github.com/go-gitea/gitea/pull/22170)
  • Multiple improvements for comment edit diff (https://github.com/go-gitea/gitea/pull/21990) (https://github.com/go-gitea/gitea/pull/22007)
  • Fix button in branch list, avoid unexpected page jump before restore branch actually done (https://github.com/go-gitea/gitea/pull/21562) (https://github.com/go-gitea/gitea/pull/21928)
  • Fix flex layout for repo list icons (https://github.com/go-gitea/gitea/pull/21896) (https://github.com/go-gitea/gitea/pull/21920)
  • Fix vertical align of committer avatar rendered by email address (https://github.com/go-gitea/gitea/pull/21884) (https://github.com/go-gitea/gitea/pull/21918)
  • Fix setting HTTP headers after write (https://github.com/go-gitea/gitea/pull/21833) (https://github.com/go-gitea/gitea/pull/21877)
  • Color and Style enhancements (https://github.com/go-gitea/gitea/pull/21784, #21799) (https://github.com/go-gitea/gitea/pull/21868)
  • Ignore line anchor links with leading zeroes (https://github.com/go-gitea/gitea/pull/21728) (https://github.com/go-gitea/gitea/pull/21776)
  • Quick fixes monaco-editor error: "vs.editor.nullLanguage" (https://github.com/go-gitea/gitea/pull/21734) (https://github.com/go-gitea/gitea/pull/21738)
  • Use CSS color-scheme instead of invert (https://github.com/go-gitea/gitea/pull/21616) (https://github.com/go-gitea/gitea/pull/21623)
  • Respect user's locale when rendering the date range in the repo activity page (https://github.com/go-gitea/gitea/pull/21410)
  • Change commits-table column width (https://github.com/go-gitea/gitea/pull/21564)
  • Refactor git command arguments and make all arguments to be safe to be used (https://github.com/go-gitea/gitea/pull/21535)
  • CSS color enhancements (https://github.com/go-gitea/gitea/pull/21534)
  • Add link to user profile in markdown mention only if user exists (https://github.com/go-gitea/gitea/pull/21533, #21554)
  • Add option to skip index dirs (https://github.com/go-gitea/gitea/pull/21501)
  • Diff file tree tweaks (https://github.com/go-gitea/gitea/pull/21446)
  • Localize all timestamps (https://github.com/go-gitea/gitea/pull/21440)
  • Add code highlighting in issue titles (https://github.com/go-gitea/gitea/pull/21432)
  • Use Name instead of DisplayName in LFS Lock (https://github.com/go-gitea/gitea/pull/21415)
  • Consolidate more CSS colors into variables (https://github.com/go-gitea/gitea/pull/21402)
  • Redirect to new repository owner (https://github.com/go-gitea/gitea/pull/21398)
  • Use ISO date format instead of hard-coded English date format for date range in repo activity page (https://github.com/go-gitea/gitea/pull/21396)
  • Use weighted algorithm for string matching when finding files in repo (https://github.com/go-gitea/gitea/pull/21370)
  • Show private data in feeds (https://github.com/go-gitea/gitea/pull/21369)
  • Refactor parseTreeEntries, speed up tree list (https://github.com/go-gitea/gitea/pull/21368)
  • Add GET and DELETE endpoints for Docker blob uploads (https://github.com/go-gitea/gitea/pull/21367)
  • Add nicer error handling on template compile errors (https://github.com/go-gitea/gitea/pull/21350)
  • Add stat to ToCommit function for speed (https://github.com/go-gitea/gitea/pull/21337)
  • Support instance-wide OAuth2 applications (https://github.com/go-gitea/gitea/pull/21335)
  • Record OAuth client type at registration (https://github.com/go-gitea/gitea/pull/21316)
  • Add new CSS variables --color-accent and --color-small-accent (https://github.com/go-gitea/gitea/pull/21305)
  • Improve error descriptions for unauthorized_client (https://github.com/go-gitea/gitea/pull/21292)
  • Case-insensitive "find files in repo" (https://github.com/go-gitea/gitea/pull/21269)
  • Consolidate more CSS rules, fix inline code on arc-green (https://github.com/go-gitea/gitea/pull/21260)
  • Log real ip of requests from ssh (https://github.com/go-gitea/gitea/pull/21216)
  • Save files in local storage as group readable (https://github.com/go-gitea/gitea/pull/21198)
  • Enable fluid page layout on medium size viewports (https://github.com/go-gitea/gitea/pull/21178)
  • File header tweaks (https://github.com/go-gitea/gitea/pull/21175)
  • Added missing headers on user packages page (https://github.com/go-gitea/gitea/pull/21172)
  • Display image digest for container packages (https://github.com/go-gitea/gitea/pull/21170)
  • Skip dirty check for team forms (https://github.com/go-gitea/gitea/pull/21154)
  • Keep path when creating a new branch (https://github.com/go-gitea/gitea/pull/21153)
  • Remove fomantic image module (https://github.com/go-gitea/gitea/pull/21145)
  • Make labels clickable in the comments section. (https://github.com/go-gitea/gitea/pull/21137)
  • Sort branches and tags by date descending (https://github.com/go-gitea/gitea/pull/21136)
  • Better repo API unit checks (https://github.com/go-gitea/gitea/pull/21130)
  • Improve commit status icons (https://github.com/go-gitea/gitea/pull/21124)
  • Limit length of repo description and repo url input fields (https://github.com/go-gitea/gitea/pull/21119)
  • Show .editorconfig errors in frontend (https://github.com/go-gitea/gitea/pull/21088)
  • Allow poster to choose reviewers (https://github.com/go-gitea/gitea/pull/21084)
  • Remove black labels and CSS cleanup (https://github.com/go-gitea/gitea/pull/21003)
  • Make e-mail sanity check more precise (https://github.com/go-gitea/gitea/pull/20991)
  • Use native inputs in whitespace dropdown (https://github.com/go-gitea/gitea/pull/20980)
  • Enhance package date display (https://github.com/go-gitea/gitea/pull/20928)
  • Display total blob size of a package version (https://github.com/go-gitea/gitea/pull/20927)
  • Show language name on hover (https://github.com/go-gitea/gitea/pull/20923)
  • Show instructions for all generic package files (https://github.com/go-gitea/gitea/pull/20917)
  • Refactor AssertExistsAndLoadBean to use generics (https://github.com/go-gitea/gitea/pull/20797)
  • Move the official website link at the footer of gitea (https://github.com/go-gitea/gitea/pull/20777)
  • Add support for full name in reverse proxy auth (https://github.com/go-gitea/gitea/pull/20776)
  • Remove useless JS operation for relative time tooltips (https://github.com/go-gitea/gitea/pull/20756)
  • Replace some icons with SVG (https://github.com/go-gitea/gitea/pull/20741)
  • Change commit status icons to SVG (https://github.com/go-gitea/gitea/pull/20736)
  • Improve single repo action for issue and pull requests (https://github.com/go-gitea/gitea/pull/20730)
  • Allow multiple files in generic packages (https://github.com/go-gitea/gitea/pull/20661)
  • Add option to create new issue from /issues page (https://github.com/go-gitea/gitea/pull/20650)
  • Background color of private list-items updated (https://github.com/go-gitea/gitea/pull/20630)
  • Added search input field to issue filter (https://github.com/go-gitea/gitea/pull/20623)
  • Increase default item listing size ISSUE_PAGING_NUM to 20 (https://github.com/go-gitea/gitea/pull/20547)
  • Modify milestone search keywords to be case insensitive again (https://github.com/go-gitea/gitea/pull/20513)
  • Show hint to link package to repo when viewing empty repo package list (https://github.com/go-gitea/gitea/pull/20504)
  • Add Tar ZSTD support (https://github.com/go-gitea/gitea/pull/20493)
  • Make code review checkboxes clickable (https://github.com/go-gitea/gitea/pull/20481)
  • Add "X-Gitea-Object-Type" header for GET /raw/ & /media/ API (https://github.com/go-gitea/gitea/pull/20438)
  • Display project in issue list (https://github.com/go-gitea/gitea/pull/20434)
  • Prepend commit message to template content when opening a new PR (https://github.com/go-gitea/gitea/pull/20429)
  • Replace fomantic popup module with tippy.js (https://github.com/go-gitea/gitea/pull/20428)
  • Allow to specify colors for text in markup (https://github.com/go-gitea/gitea/pull/20363)
  • Allow access to the Public Organization Member lists with minimal permissions (https://github.com/go-gitea/gitea/pull/20330)
  • Use default values when provided values are empty (https://github.com/go-gitea/gitea/pull/20318)
  • Vertical align navbar avatar at middle (https://github.com/go-gitea/gitea/pull/20302)
  • Delete cancel button in repo creation page (https://github.com/go-gitea/gitea/pull/21381)
  • Include login_name in adminCreateUser response (https://github.com/go-gitea/gitea/pull/20283)
  • fix: icon margin in user/settings/repos (https://github.com/go-gitea/gitea/pull/20281)
  • Remove blue text on migrate page (https://github.com/go-gitea/gitea/pull/20273)
  • Modify milestone search keywords to be case insensitive (https://github.com/go-gitea/gitea/pull/20266)
  • Move some files into models' sub packages (https://github.com/go-gitea/gitea/pull/20262)
  • Add tooltip to repo icons in explore page (https://github.com/go-gitea/gitea/pull/20241)
  • Remove deprecated licenses (https://github.com/go-gitea/gitea/pull/20222)
  • Webhook for Wiki changes (https://github.com/go-gitea/gitea/pull/20219)
  • Share HTML template renderers and create a watcher framework (https://github.com/go-gitea/gitea/pull/20218)
  • Allow enable LDAP source and disable user sync via CLI (https://github.com/go-gitea/gitea/pull/20206)
  • Adds a checkbox to select all issues/PRs (https://github.com/go-gitea/gitea/pull/20177)
  • Refactor i18n to locale (https://github.com/go-gitea/gitea/pull/20153)
  • Disable status checks in template if none found (https://github.com/go-gitea/gitea/pull/20088)
  • Allow manager logging to set SQL (https://github.com/go-gitea/gitea/pull/20064)
  • Add order by for assignee no sort issue (https://github.com/go-gitea/gitea/pull/20053)
  • Take a stab at porting existing components to Vue3 (https://github.com/go-gitea/gitea/pull/20044)
  • Add doctor command to write commit-graphs (https://github.com/go-gitea/gitea/pull/20007)
  • Add support for authentication based on reverse proxy email (https://github.com/go-gitea/gitea/pull/19949)
  • Enable spellcheck for EasyMDE, use contenteditable mode (https://github.com/go-gitea/gitea/pull/19776)
  • Allow specifying SECRET_KEY_URI, similar to INTERNAL_TOKEN_URI (https://github.com/go-gitea/gitea/pull/19663)
  • Rework mailer settings (https://github.com/go-gitea/gitea/pull/18982)
  • Add option to purge users (https://github.com/go-gitea/gitea/pull/18064)
  • Add author search input (https://github.com/go-gitea/gitea/pull/21246)
  • Make rss/atom identifier globally unique (https://github.com/go-gitea/gitea/pull/21550)
• BUGFIXES
  • Auth interface return error when verify failure (https://github.com/go-gitea/gitea/pull/22119) (https://github.com/go-gitea/gitea/pull/22259)
  • Use complete SHA to create and query commit status (https://github.com/go-gitea/gitea/pull/22244) (https://github.com/go-gitea/gitea/pull/22257)
  • Update bleve and zapx to fix unaligned atomic (https://github.com/go-gitea/gitea/pull/22031) (https://github.com/go-gitea/gitea/pull/22218)
  • Prevent panic in doctor command when running default checks (https://github.com/go-gitea/gitea/pull/21791) (https://github.com/go-gitea/gitea/pull/21807)
  • Load GitRepo in API before deleting issue (https://github.com/go-gitea/gitea/pull/21720) (https://github.com/go-gitea/gitea/pull/21796)
  • Ignore line anchor links with leading zeroes (https://github.com/go-gitea/gitea/pull/21728) (https://github.com/go-gitea/gitea/pull/21776)
  • Set last login when activating account (https://github.com/go-gitea/gitea/pull/21731) (https://github.com/go-gitea/gitea/pull/21755)
  • Fix UI language switching bug (https://github.com/go-gitea/gitea/pull/21597) (https://github.com/go-gitea/gitea/pull/21749)
  • Quick fixes monaco-editor error: "vs.editor.nullLanguage" (https://github.com/go-gitea/gitea/pull/21734) (https://github.com/go-gitea/gitea/pull/21738)
  • Allow local package identifiers for PyPI packages (https://github.com/go-gitea/gitea/pull/21690) (https://github.com/go-gitea/gitea/pull/21727)
  • Deal with markdown template without metadata (https://github.com/go-gitea/gitea/pull/21639) (https://github.com/go-gitea/gitea/pull/21654)
  • Fix opaque background on mermaid diagrams (https://github.com/go-gitea/gitea/pull/21642) (https://github.com/go-gitea/gitea/pull/21652)
  • Fix repository adoption on Windows (https://github.com/go-gitea/gitea/pull/21646) (https://github.com/go-gitea/gitea/pull/21650)
  • Sync git hooks when config file path changed (https://github.com/go-gitea/gitea/pull/21619) (https://github.com/go-gitea/gitea/pull/21626)
  • Fix 500 on PR files API (https://github.com/go-gitea/gitea/pull/21602) (https://github.com/go-gitea/gitea/pull/21607)
  • Fix Timestamp.IsZero (https://github.com/go-gitea/gitea/pull/21593) (https://github.com/go-gitea/gitea/pull/21603)
  • Fix viewing user subscriptions (https://github.com/go-gitea/gitea/pull/21482)
  • Fix mermaid-related bugs (https://github.com/go-gitea/gitea/pull/21431)
  • Fix branch dropdown shifting on page load (https://github.com/go-gitea/gitea/pull/21428)
  • Fix default theme-auto selector when nologin (https://github.com/go-gitea/gitea/pull/21346)
  • Fix and improve incorrect error messages (https://github.com/go-gitea/gitea/pull/21342)
  • Fix formatted link for PR review notifications to matrix (https://github.com/go-gitea/gitea/pull/21319)
  • Center-aligning content of WebAuthN page (https://github.com/go-gitea/gitea/pull/21127)
  • Remove follow from commits by file (https://github.com/go-gitea/gitea/pull/20765)
  • Fix commit status popup (https://github.com/go-gitea/gitea/pull/20737)
  • Fix init mail render logic (https://github.com/go-gitea/gitea/pull/20704)
  • Use correct page size for link header pagination (https://github.com/go-gitea/gitea/pull/20546)
  • Preserve unix socket file (https://github.com/go-gitea/gitea/pull/20499)
  • Use tippy.js for context popup (https://github.com/go-gitea/gitea/pull/20393)
  • Add missing parameter for error in log message (https://github.com/go-gitea/gitea/pull/20144)
  • Do not allow organisation owners add themselves as collaborator (https://github.com/go-gitea/gitea/pull/20043)
  • Rework file highlight rendering and fix yaml copy-paste (https://github.com/go-gitea/gitea/pull/19967)
  • Improve code diff highlight, fix incorrect rendered diff result (https://github.com/go-gitea/gitea/pull/19958)
• TESTING
  • Improve OAuth integration tests (https://github.com/go-gitea/gitea/pull/21390)
  • Add playwright tests (https://github.com/go-gitea/gitea/pull/20123)
• BUILD
  • Switch to building with go1.19 (https://github.com/go-gitea/gitea/pull/20695)
  • Update JS dependencies, adjust eslint (https://github.com/go-gitea/gitea/pull/20659)
  • Add more linters to improve code readability (https://github.com/go-gitea/gitea/pull/19989)

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.