(cherry picked from commitb07123ee7b
) (cherry picked from commitca85c880b4
) (cherry picked from commit723ead94cb
) (cherry picked from commitff148318da
) [DOCS] RELEASE-NOTES: 1.19.0 (cherry picked from commite84e43887b
) [DOCS] RELEASE-NOTES: add scoped access tokens (cherry picked from commit688f831853
) [DOCS] RELEASE-NOTES: Scoped labels (cherry picked from commit747479a07b
) [DOCS] RELEASE-NOTES: OIDC groups (cherry picked from commit10c505fe89
) [DOCS] RELEASE-NOTES: Copy Link is broken On firefox it fails with Uncaught TypeError: navigator.clipboard is undefined On chromium it fails with Uncaught TypeError: Cannot read properties of undefined (reading 'writeText') (cherry picked from commit148b2ff093
) [DOCS] RELEASE-NOTES: Copy citation (cherry picked from commitd0f217735f
) [DOCS] RELEASE-NOTES: Support org/user level projects (cherry picked from commitde845c7bcf
) [DOCS] RELEASE-NOTES: v1.19 has a documentation (cherry picked from commit9a5b46da32
) [DOCS] RELEASE-NOTES: do not split webhook section (cherry picked from commit00ed020321
) [DOCS] RELEASE-NOTES: Incoming emails (cherry picked from commit06c455b33b
) [DOCS] RELEASE-NOTES: secrets are an implementation detail (cherry picked from commit8236dc3a57
) [DOCS] RELEASE-NOTES: Prohibit fork if user reached maximum (cherry picked from commit0f80b8c696
) [DOCS] RELEASE-NOTES: scoped tokens: do not duplicate the docs (cherry picked from commit9bc4793c07
) [DOCS] RELEASE-NOTES: rss feed for tags and releases (cherry picked from commit599b36fada
) [DOCS] RELEASE-NOTES: protected branches wildcard (cherry picked from commit2b316c4950
) [DOCS] RELEASE-NOTES: disable releases (cherry picked from commit9a60773f1d
) [DOCS] RELEASE-NOTES: review box (cherry picked from commit09867dd122
) [DOCS] RELEASE-NOTES: asciicast support (cherry picked from commitea9658379b
) [DOCS] RELEASE-NOTES: attention blocks (cherry picked from commit70b387750b
) [DOCS] RELEASE-NOTES: commit cross reference (cherry picked from commitfe706dad13
) [DOCS] RELEASE-NOTES: strip user completion border case (cherry picked from commit33ca51b4b6
) [DOCS] RELEASE-NOTES: card preview (cherry picked from commit626cd78ca6
) [DOCS] RELEASE-NOTES: raw copy button (cherry picked from commitedfb467d64
) [DOCS] RELEASE-NOTES: allow edits by maintainers by default (cherry picked from commit7006405bc6
) [DOCS] RELEASE-NOTES: database auto migration is a little arcane (cherry picked from commit78030fa9af
) [DOCS] RELEASE-NOTES: fix typos & minor rewording (cherry picked from commitae1d47f656
) (cherry picked from commitad08ca9955
) [DOCS] RELEASE-NOTES: webhook authorization header (cherry picked from commitc35e2c4f6f
) [DOCS] RELEASE-NOTES: video element in markdown (cherry picked from commitbcb0bd51d2
) [DOCS] RELEASE-NOTES: move scoped labels to the documentation (cherry picked from commitc5eedaf4f3
) [DOCS] RELEASE-NOTES: cosmetic improvements (cherry picked from commitb93df350d9
) [DOCS] RELEASE-NOTES: 1.19.0-0 is really : 1.19.0-2 (cherry picked from commit60d770c2c9
) [DOCS] RELEASE-NOTES: relevant repositories (cherry picked from commitde6ed5b87f
) (cherry picked from commit71d91fdf22
) [DOCS] RELEASE-NOTES: semantic version (cherry picked from commitaf062d77f0
) [DOCS] RELEASE-NOTES: reflogs (cherry picked from commit084713d8aa
) (cherry picked from commit90ad322a56
) [DOCS] RELEASE-NOTES: fix broken link to OIDC mapping (cherry picked from commit802a252eb5
) [DOCS] RELEASE-NOTES: Fix spaces (cherry picked from commita605d36ab6
) [DOCS] RELEASE-NOTES: SemVer (cherry picked from commit7b29c90035
) (cherry picked from commit82799195c9
) (cherry picked from commit5d9c2e9ec6
) [DOCS] RELEASE-NOTES: 1.19.0-3 (cherry picked from commitc599b2947d
) (cherry picked from commit8a37027ae7
) [DOCS] RELEASE-NOTES: v1.19.1-0 (cherry picked from commit89b9e96cc7
) (cherry picked from commit2b4e881a4e
) [DOCS] RELEASE-NOTES: 1.19.2-0 (cherry picked from commit0c0d2ec46c
) (cherry picked from commit437b8caae4
) [DOCS] RELEASE-NOTES: 1.19.3-0 (cherry picked from commit040740917e
) [DOCS] RELEASE-NOTES: 1.19.3-0 (fix typo) (cherry picked from commit24516cb22a
) (cherry picked from commit429c8e6525
) (cherry picked from commit8247bddb45
) (cherry picked from commitd77d7b7be7
) (cherry picked from commita64c899b1d
) (cherry picked from commit0803eaa2e3
) (cherry picked from commit8538f2897e
) (cherry picked from commit45b9037d3c
) (cherry picked from commit928705f870
) (cherry picked from commit19e683468c
) (cherry picked from commit5ae55e8e34
) (cherry picked from commit7c224d84cf
) [DOCS] RELEASE-NOTES: 1.20.0 (cherry picked from commit3fbcdd235b
) (cherry picked from commite7a621acae
) (cherry picked from commit70adac6d66
) [DOCS] RELEASE-NOTES: 1.20.0-0-rc0 (squash) rewording (cherry picked from commit1b79fab57d
) [DOCS] RELEASE-NOTES: 1.20.0-0-rc0 (squash) time (cherry picked from commitcfd599a132
) [DOCS] RELEASE-NOTES: 1.20.0-0-rc0 (squash) wiki (cherry picked from commit6aa2ab41c6
) pick changes from #829 (cherry picked from commitf599598101
) [DOCS] RELEASE-NOTES: 1.20.0-0-rc0 (squash) ui (cherry picked from commit5f0aa769b1
) features (cherry picked from commitd1e788ff4e
) typos (cherry picked from commit088d4b2d61
) Mirror Settings (cherry picked from commit161412affd
) features (cherry picked from commit10cb0379e2
) fix typo (cherry picked from commitaee096b040
) TODO (cherry picked from commit0d4e0bb4a9
) typo (cherry picked from commitb76a3c1a84
) (cherry picked from commit4c354196c2
) (cherry picked from commit6323c6d1a2
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) Woodpecker CI archive repository (cherry picked from commit154ee5bc9c
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) (cherry picked from commit656f955448
) [DOCS] RELEASE-NOTES: 1.19.4-0 (cherry picked from commit85bd997176
) [DOCS] RELEASE-NOTES: 1.19.4-0 (squash) fix typo (cherry picked from commite5c364c586
) (cherry picked from commitc123048e51
) (cherry picked from commitad2fedb693
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) blog Pick changes from https://blog.gitea.com/release-of-1.20.0/ (cherry picked from commitc8068a9d7b
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) Gitea release notes Review https://github.com/go-gitea/gitea/releases/tag/v1.20.0 (cherry picked from commitdd58b50403
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) commits git log --no-merges --oneline 64ed262e1..gitea/release/v1.20 . ':(exclude,glob)docs/**' ':(exclude)CONTRIBUTING.md' ':(exclude)MAINTAINERS' ':(exclude,glob).github/**' ':(exclude)CHANGELOG.md' ':(exclude,glob)options/locale/**' ':(exclude,glob)options/license/**' ':(exclude,glob)snap/**' ':(exclude).drone.yml' ':(exclude)custom/conf/app.example.ini'9159964ad
Avoid opening/closing PRs which are already merged (#25883) (#25903)9369b3831
Skip unuseful error message in dev mode when watching local filesystem (#25919) (#25927)6e82d0bb7
Add shutting down notice (#25920) (#25922)36b9a86bd
Fix incorrect milestone count when provide a keyword (#25880) (#25904)de8127e78
fix incorrect repo url when changed the case of ownername (#25733) (#25881)de8127e78
fix incorrect repo url when changed the case of ownername (#25733) (#25881)186f07bbf
Make `add line comment` buttons focusable (#25894) (#25896)45b1f4dd3
Add support for different Maven POM encoding (#25873) (#25890)026e745b9
Fix incorrect release count (#25879) (#25887)c334be828
Fix empty project displayed in issue sidebar (#25802) (#25854)353dcc5ad
Fix the error message when the token is incorrect (#25701) (#25836)abe9c641c
Show correct SSL Mode on "install page" (#25818) (#25838)052e65e63
Fix incorrect oldest sort in project list (#25806) (#25835)c1a10be07
Fix activity type match in `matchPullRequestEvent` (#25746) (#25796)2b79d3fd5
For API attachments, use API URL (#25639) (#25814)b4460cf54
Make "install page" respect environment config (#25648) (#25799)a1bc2aa05
Avoid amending the Rebase and Fast-forward merge if there is no message template (#25779) (#25809)d713cf615
Fix WORK_DIR for docker (root) image (#25738) (#25811)012b804a9
Clarify "text-align" CSS helpers, fix clone button padding (#25763) (#25764)372b622c2
Revert package access change from #23879 (#25707) (#25785)06bcdfe77
Remove unused code (#25734) (#25788)a5a3c8141
Fix notification list bugs (#25781) (#25787)ea2c9de3c
Test if container blob is accessible before mounting (#22759) (#25784)348a6bf70
Always pass 6-digit hex color to monaco (#25780) (#25782)91dadeddd
Translate untranslated string in issues list (#25759) (#25761)32eaba1b4
Hide `add file` button for pull mirrors (#25748) (#25751)917ca5ded
Several fixes for mobile UI (#25634) (#25689)e595dfeec
Allow/fix review (approve/reject) of empty PRs (#25690) (#25732)03cacf971
Check `ctx.Written()` for `GetActionIssue` (#25698) (#25711)68e0c802f
Show correct naming for 1 comment (#25704) (#25712)09668b2e2
Correct permissions for `.ssh` and `authorized_keys` (#25721) (#25730)04eea29ec
Fix tags header and pretty format numbers (#25624) (#25694)511be9fe6
Fix position of org follow button (#25688) (#25692)24e64fe37
Replace `interface{}` with `any` (#25686) (#25687)4e310133f
Prevent duplicate image loading (#25675) (#25684)491f36d32
Actions list enhancements (#25601) (#25678)5510ed34f
Fix the nil pointer when assigning issues to projects (#25665) (#25677)39fce5750
Prevent SVG shrinking (#25652) (#25669)1f9037604
Fix show more for image on diff page (#25672) (#25673)0af6542a3
Add unit test for repository collaboration (#25640) (#25658)69bdcf41f
Log the real reason when authentication fails (but don't show the user) (#25414) (#25660)e610b0389
Fix UI misalignment on user setting page (#25629) (#25656)13ffa287b
Fix bug of branches API with tests(#25578) (#25579) (cherry picked from commit3e9e862e5e
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) reorder breaking (cherry picked from commit4e4cdddc55
) address rome-user review (cherry picked from commit8791fe88b1
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) reword breaking - removed the section about the changed themes: it is an internal detail and redundant with the above warning regarding themes & templates (cherry picked from commitb34e9a7b19
) [DOCS] RELEASE-NOTES: 1.20.0 (squash) minor rewording The CI & Actions sections were grouped together. (cherry picked from commited236e1ee8
) [DOCS] RELEASE-NOTES: 1.20.1-0 (squash) (cherry picked from commit3c11eb1de5
) [DOCS] RELEASE-NOTES: 1.20.1-0 (squash) Forgejo features/optimizations (cherry picked from commitc516fd0c7a
) [DOCS] RELEASE-NOTES: 1.20.1-0 (squash) fix typo in Alpine version (cherry picked from commit1c2a5b5162
) [DOCS] RELEASE-NOTES: 1.20.1-0 (squash) comment out obsoleted queue keys (cherry picked from commit8c0d9459c5
) [DOCS] RELEASE-NOTES: 1.20.1-0 (squash) WORK_PATH breaking change (cherry picked from commitf4ea3b27f5
) (cherry picked from commit0557568f61
) [DOCS] RELEASE-NOTES.md (squash) obsolete queue `app.ini` keys (cherry picked from commite0c943ac3b
) [DOCS] RELEASE-NOTES.md (squash) v1.20.2-0 (cherry picked from commitf2c654d1c8
) [DOCS] RELEASE-NOTES.md (squash) fix LFS issue link (cherry picked from commit2461355f2a
) (cherry picked from commit750652d75a
) (cherry picked from commit6899dbdc11
) (cherry picked from commit88b988d084
) [DOCS] RELEASE-NOTES.md (squash) v1.20.3-0 (cherry picked from commitd566e78d68
) (cherry picked from commit65439eafa4
) (cherry picked from commita76cc5b8bc
) (cherry picked from commitb4e1ad6020
) [DOCS] RELEASE-NOTES.md (squash) v1.20.4-0 (cherry picked from commit8a910c0c33
) [DOCS] RELEASE-NOTES.md (squash) link to upgrade docs Refs: https://codeberg.org/forgejo/forgejo/issues/1199 (cherry picked from commitd4e9030873
) (cherry picked from commit7da7b9cef4
) (cherry picked from commit73b64ea895
) [DOCS] RELEASE-NOTES.md (squash) v1.20.4-1 [DOCS] RELEASE-NOTES.md (squash) v1.21.0-0 (cherry picked from commite618ea55a5
) (cherry picked from commitf3ee986416
) [DOCS] RELEASE-NOTES.md (squash) 1.20.5-0 (cherry picked from commitce5541c78b
) [DOCS] RELEASE-NOTES.md (squash) 1.20.5-0 is a security release (cherry picked from commit5dd66c06e3
) slug of the blog post changed (cherry picked from commitfc5b52049f
) apply caesar rewording suggestions (cherry picked from commit59e9648b71
) [DOCS] RELEASE-NOTES.md (squash) typo (cherry picked from commite8daead2a1
)
113 KiB
Release Notes
A Forgejo release is published shortly after a Gitea release is published and they have matching release numbers. Additional Forgejo releases may be published to address urgent security issues or bug fixes.
The Forgejo admin should carefully read the required manual actions before upgrading. A point release (e.g. v1.21.1-0 or v1.21.2-0) does not require manual actions but others might (e.g. v1.20, v1.21).
1.21.0-0 (DRAFT)
The complete list of commits included in the Forgejo v1.21.0-0
release can be reviewed from the command line with:
$ git clone 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).
- Restrict certificate type for builtin SSH server. This is a breaking change for setups where the builtin SSH server is being used and for some reason host certificates were being used for authentication.
- Some Forgejo CLI options have changed and scripts may need to be updated. For instance
--verbose
is no longer a global option and is implemented on a per sub-command basis. Checkforgejo --help
orforgejo docs
for more information. - Remove "CHARSET" config option for MySQL and always use "utf8mb4". It has been a requirement for years and specifying anything else is likely to cause issues.
- Set SSH_AUTHORIZED_KEYS_BACKUP to false by default. There is no automatic cleanup of these backups and can end up using a significant amount of disk space over time.
(More items to be added here)
1.20.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.
-
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 thedeleted_branch
table is missing although it should not. - Fix the release URL in webhooks so that
URL
points to the API URL andHTMLURL
points to the web page. - Fix organization field being null in POST /orgs/{orgid}/teams.
- Fix the display of pull requests waiting for review on the
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.
-
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.
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.
-
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.
-
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
- Fix some bugs in how the storage sections are interpreted in the
-
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.
-
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
orprivate
. - 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 ofenvironment-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>
inapp.ini
. Check the documentation andapp.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 theapp.ini
file is writable by the user under which the Forgejo server runs andWORK_PATH
is not set, the server will add it. Otherwise it will log an error starting withUnable to update WORK_PATH
. One of the consequences of not settingWORK_PATH
inapp.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 inapp.ini
now defaults to using the Go SSH key parsing instead of thessh-keygen
binary. WhenSTART_SSH_SERVER
is true, the decision to use the Go SSH key parsing or an external binary will now depend on the value ofSSH_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
- 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 eitherClose issue
orClose 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
- 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
- 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
andverification
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 ifmarkdown.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 withactions register
for the Forgejo runner. - When called as
forgejo-cli
(withln -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 instanceFORGEJO__security__INTERNAL_TOKEN__FILE=/etc/forgejo/token
can be used instead ofFORGEJO__security__INTERNAL_TOKEN=tokenvalue
. - The new
[git.config]
section ofapp.ini
is used togit 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.
- Any URL scheme may be used for links. Previously, non-standard URLs (like matrix:) were not rendered unless explicitly listed in
- 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.
-
The semantic version was updated from
4.2.1+0-gitea-1.19.3
to4.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 ifForgejo 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 of500
- 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 error500
- 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
- Fix an edge case where a user changing their
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.
-
The semantic version was updated from
4.2.0+0-gitea-1.19.2
to4.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.
-
The semantic version was updated from
4.1.0+0-gitea-1.19.1
to4.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.
- 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:
-
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.
-
The semantic version was updated from
4.0.0+0-gitea-1.19.0
to4.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 ofgolang: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.
- 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
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.
-
The semantic version was updated from
3.0.0+0-gitea-1.19.0
to4.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 theDISABLED_REPO_UNITS
orDEFAULT_REPO_UNITS
configuration variables must be replaced withrepo.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
-
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 thescopes: ['all', 'sudo']
parameter and theforgejo admin user generate-access-token
will require the--scopes all,sudo
argument obtain tokens with ulimited access as before for admin users. -
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 asDEFAULT_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
andgitea-actions
, they will also need to be renamed before the upgrade. They are now reserved names for the experimental internal CI/CD namedActions
. -
Since v1.18.5, in addition to the Forgejo release number, a semantic version number (e.g.
v3.0.0
) can be obtained from thenumber
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 theversion
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.
-
Webhook authorization header Forgejo webhooks can be configured to send an authorization header to the target.
-
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
-
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 tofalse
so forks are prohibited if that means exceeding the quota. -
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".
-
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 theMyForgejoTeam1
andMyForgejoTeam2
teams in theMyForgejoOrganization
organization. This mapping is set when adding a newAuthentication Source
in theSite Administration
panel....
-
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*
. -
Garbage collect LFS Add a doctor command for full garbage collection of LFS:
forgejo doctor --run gc-lfs
. -
Additions to the API
-
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.
-
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 thesrc
,autoplay
, andcontrols
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 theCite 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. -
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.
-
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)
- Use
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)
- Add
- BUGFIXES
- Update
github.com/zeripath/zapx/v15
(https://github.com/go-gitea/gitea/pull/22485) - Fix pull request API field
closed_at
always beingnull
(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)
- Update
- 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.
![Landing page](/mirrors/forgejo/media/commit/079e0efb011b761b1948623b26737d55ad2e6b36/releases/images/forgejo-v1.18.0-rc1-2-landing.jpg)
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
tolocale
(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
toToCommit
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
tolocale
(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.