.gitignore

@@ -1,5 +1,6 @@
 public/
 themes/
+.hugo_build.lock
 
 # GoLand
-.idea/
+.idea/

content/post/release-of-1.17.0.md

@@ -1,14 +1,13 @@
 ---
 date: "2022-07-30T21:30:19+07:00"
-author: ["gusted", "delvh", "noerw"]
+author: Gusted
 title: "Gitea 1.17.0 is released"
 tags: ["release"]
 draft: false
 ---
 
 We are proud to present the release of Gitea version 1.17.0, a relatively big release with a lot of new and exciting features and plenty breaking changes.
-
-We highly encourage users to update to this version after careful reading about the breaking changes for some important bug-fixes.
+We highly encourage users to update to this version after carefully reading about the breaking changes for some important bug-fixes.
 
 [645](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+milestone%3A1.17.0+is%3Amerged) Pull Requests were merged to release this version.
 
@@ -16,11 +15,15 @@ You can download one of our pre-built binaries from our [downloads page](https:/
   
 We would also like to thank all of our supporters on [Open Collective](https://opencollective.com/gitea) who are helping to sustain us financially.
 
+Read on to learn about major new features and breaking changes.
+
 <!-- this is the indicator for the static site generator for where to stop the preview in the post list -->
 <!--more-->
 
 **Have you heard? We now have a [swag shop](https://shop.gitea.io)! :shirt: :tea:**
 
+---
+
 ## Major New Features
 
 ### Package Registry ([#16510](https://github.com/go-gitea/gitea/pull/16510))
@@ -37,13 +40,15 @@ Instead, Gitea now provides a handy UI for these tasks!
 
 | | |
 |-|-|
-| ![screenshot 1](https://blog.gitea.io/demos/17902/2.png) | ![screenshot 2](https://blog.gitea.io/demos/17902/1.png) |
+| ![screenshot 1](/demos/17902/2.png) | ![screenshot 2](/demos/17902/1.png) |
 
 ### Better Mobile Experience ([#19546](https://github.com/go-gitea/gitea/pull/19546) et al.)
 
 [@Gusted](https://github.com/Gusted) worked to significantly improve the mobile experience of Gitea:
 A lot of the frontend has been refactored without making major changes to the current UI.
+
 It now has a more responsive design, hence making browsing Gitea on mobile phones a more pleasant experience!
+
 Check out the linked Pull Request for a demo & comparison of the updated layouts.
 
 ### Improved file navigation ([#19007](https://github.com/go-gitea/gitea/pull/19007) & [#15028](https://github.com/go-gitea/gitea/pull/15028))
@@ -51,49 +56,46 @@ Check out the linked Pull Request for a demo & comparison of the updated layouts
 Navigating many files is often a struggle.
 This release features some workflow improvements you may already know from other forges:
 
-- During PR review, you can now mark changed files as reviewed ([#19007](https://github.com/go-gitea/gitea/pull/19007)).  
-  - If a file has been changed since it was last reviewed, the changed files will be visually marked
-  - Unlike GitHub, this label is also added for newly added unseen files
-  - You can watch a demo in the linked Pull Request
+- During PR review, you can now mark changed files as reviewed and be informed about later changes to them ([#19007](https://github.com/go-gitea/gitea/pull/19007)).
+  You can watch a demo in the linked Pull Request
 
-- [@rogerluo410](https://github.com/rogerluo410) implemented a *Go to file* feature for the repo code listing a while ago, which was ready to merge after additional work by [@wxiaoguang](https://github.com/wxiaoguang) ([#15028](https://github.com/go-gitea/gitea/pull/15028))
-  ![go to file demo](https://blog.gitea.io/demos/15028/1.gif)
+- [@rogerluo410](https://github.com/rogerluo410) and [@wxiaoguang](https://github.com/wxiaoguang) implemented a *Go to file* feature for the repo code listing ([#15028](https://github.com/go-gitea/gitea/pull/15028))
+  ![go to file demo](/demos/15028/1.gif)
 
-### More RSS Feeds ([#17714](https://github.com/go-gitea/gitea/pull/17714) & [#19055](https://github.com/go-gitea/gitea/pull/19055))
+### More RSS feeds ([#17714](https://github.com/go-gitea/gitea/pull/17714) & [#19055](https://github.com/go-gitea/gitea/pull/19055))
 
 RSS-users will appreciate the new feeds for organizations and repositories that were added by [@6543](https://github.com/6543).
 
 ### Auto merge pull requests when all checks succeeded ([#19648](https://github.com/go-gitea/gitea/pull/19648)) & ([#9307](https://github.com/go-gitea/gitea/pull/9307))
 
 Thanks to [@6543](https://github.com/6543) & [@kolaente](https://github.com/kolaente), Gitea now allows you to merge a Pull request when all required checks has passed, either via the WebUI or via the API.
+Note that this feature will only be enabled when the target branch has branch protection.
 
 | | |
 |-|-|
-| ![screenshot 1](https://blog.gitea.io/demos/19648/1.png) | ![screenshot 2](https://blog.gitea.io/demos/19648/2.png) |
+| ![screenshot 1](/demos/19648/1.png) | ![screenshot 2](/demos/19648/2.png) |
 
 ### Allow edits by maintainers ([#18002](https://github.com/go-gitea/gitea/pull/18002))
 
-Thanks to [@qwerty287](https://github.com/qwerty287), Gitea now allows you to decides if maintainers of the upstream 
+Thanks to [@qwerty287](https://github.com/qwerty287), Gitea now allows you to decide if maintainers of the upstream 
 repository can push to the head branch of your PR when creating a Pull Request from a fork.
 This enables a workflow similar to how Gitea itself is maintained currently and can simplify the PR workflow for open source development.
 
 ### Permanent issue (and PR) deletion ([#19032](https://github.com/go-gitea/gitea/pull/19032))
 
-Thanks to [@fnetX](https://codeberg.org/fnetX), to combat spam and confidential information, issues (and subsequently PRs) can now be permanently deleted.
+Thanks to [@fnetX](https://codeberg.org/fnetX), to combat spam and confidential information, issues (and subsequently PRs) can now be permanently deleted.  
 A repository admin or instance admin can find the delete button at the bottom of the sidebar of the issue or pull reuqest.
 
 ### Generate table of contents in wikis ([#19873](https://github.com/go-gitea/gitea/pull/19873))
 
-Thanks to [@zeripath](https://github.com/zeripath), wiki pages now show their logical structure automatically in the sidebar.  
-This removes the need to manually maintain a ToC and helps skimming for the most important sections for you.
+Thanks to [@zeripath](https://github.com/zeripath), wiki pages now show their logical structure automatically in the sidebar. This removes the need to manually maintain a ToC and helps you to skim for the most important sections.
 
 ### Customizing the default merge style ([#19751](https://github.com/go-gitea/gitea/pull/19751))
 
-Thanks to [@ttys3](https://github.com/ttys3), Gitea now allows you to set the default merge style globally.  
-This only affects repositories that were created after the setting change.
+Thanks to [@ttys3](https://github.com/ttys3), Gitea now allows you to set the default merge style globally. This only affects repositories that were created after the setting change.
 <!-- I'd not mention this, too minor of a change. wdyt? -->
 
-### Customizing the default commit messages in PRs ([#18177](https://github.com/go-gitea/gitea/pull/18177))
+### Customizing the default commit messages ([#18177](https://github.com/go-gitea/gitea/pull/18177))
 
 Thanks to [@lunny](https://github.com/lunny), you can now set the default merge message used for merging PRs.  
 The customization files must be in `.gitea/default_merge_message/<uppercase_merge_style>_TEMPLATE.md`.  
@@ -106,15 +108,13 @@ More information on the file names and possible variables can be found [here](ht
 ### :exclamation: Internal Gitconfig ([#19732](https://github.com/go-gitea/gitea/pull/19732))
 
 Previously, Gitea used the users gitconfig (`$HOME/.gitconfig`) in addition to the system gitconfig (`/etc/gitconfig`).  
-Now, Gitea uses the system gitconfig (`/etc/gitconfig`) combined with an internal gitconfig located in `{[repository].ROOT}/.gitconfig`.  
-If you customized your user gitconfig for Gitea, you should add these customizations to one of the available gitconfigs.  
-Additional git-relevant files that are normally in your user home directory, like `$HOME/.gnupg`, should be moved/ copied to `{[repository].REPO}/` as well.
+Now, Gitea uses the system gitconfig (`/etc/gitconfig`) combined with an internal gitconfig located in `{[repository].ROOT}/.gitconfig`.
+If you customized your user gitconfig for Gitea, you should add these customizations to one of the available gitconfigs. Additional git-relevant files that are normally in your user home directory, like `$HOME/.gnupg`, should be moved/ copied to `{[repository].REPO}/` as well.
 
 ### :exclamation: Email address validation restricted ([#17688](https://github.com/go-gitea/gitea/pull/17688))
 
 With this release, Gitea restricts what is seen as a valid email:  
-Emails must only contain characters in ``a-zA-Z0-9.!#$%&'*+-/=?^_{|}`~``  
-Additionally, the first letter must be in `a-zA-Z0-9`, and after the `@`, only characters in `a-zA-Z0-9.` can follow.
+Emails must only contain characters in ``a-zA-Z0-9.!#$%&'*+-/=?^_{|}`~``. Additionally, the first letter must be in `a-zA-Z0-9`, and after the `@`, only characters in `a-zA-Z0-9.` can follow.
 
 ### :exclamation: Renamed configuration options for ACME / Let's Encrypt ([#18340](https://github.com/go-gitea/gitea/pull/18340))
 
@@ -122,28 +122,28 @@ Configuration settings have been renamed from `LETSENCRYPT` to `ACME`:
 
 - `ENABLE_LETSENCRYPT` → `ENABLE_ACME`
 - `LETSENCRYPT_URL` → `ACME_URL`
-- `LETSENCRYPT_ACCEPTTOS` → `ACME_ACCEPTTOS`
+- `LETSENCRYPT_ACCEPT_TOS` → `ACME_ACCEPT_TOS`
 - `LETSENCRYPT_DIRECTORY` → `ACME_DIRECTORY`
 - `LETSENCRYPT_EMAIL` → `ACME_EMAIL`
 
 ### :exclamation: New logger format and configuration ([#17308](https://github.com/go-gitea/gitea/pull/17308))
 
-This PR substantially changes the logging format of the router logger.
-If you use this logging for monitoring (e.g. fail2ban) you will need to update this to match the new format.
+This PR substantially changes the logging format of the router logger.  
+If you use this logging for monitoring (e.g. fail2ban) you will need to update this to match the new format.  
 Refer to the documentation on the [router logger](https://docs.gitea.io/en-us/logging-configuration/#the-router-logger) for new configuration options.
 <!-- FIXME: what exactly is the new format?! -->
 
 ### :exclamation: `main` as default branch ([#19354](https://github.com/go-gitea/gitea/pull/19354))
 
-The default value of the setting `repository.DEFAULT_BRANCH` was switched from `master` to `main`.
-If you want to continue using `master` as default branch name, set this setting.
+The default value of the setting `repository.DEFAULT_BRANCH` was switched from `master` to `main`.  
+If you want to continue using `master` as default branch name, set this setting.  
 This change is especially relevant for third party tools that assume the default branch of a repository.
 
 ### :exclamation: Change initial trust model to `committer` ([#18335](https://github.com/go-gitea/gitea/pull/18335))
 
-Previously, Gitea would by default use the `collaborator` trust model.
-This means only verified commits of collaborators can be trusted.
-This is quite an aggressive trust model, and now it has changed to match GitHub's behavior of trusting the commiter. 
+Previously, Gitea would by default use the `collaborator` trust model.  
+This means only verified commits of collaborators can be trusted.  
+This is quite an aggressive trust model, and now it has changed to match GitHub's behavior of trusting the commiter.  
 This means verified commits in a repository from non-collaborators won't be marked as unverified.
 
 If you rely on the old behavior, you must set `DEFAULT_TRUST_MODEL` to `collaborator`.
@@ -159,7 +159,7 @@ This is due to an issue with libc of the new base image alpine 3.15.
 
 ### :exclamation: Require Go >= 1.18 to compile ([#19918](https://github.com/go-gitea/gitea/pull/19918),  [#19099](https://github.com/go-gitea/gitea/pull/19099))
 
-The minimum version of Go needed to compile Gitea has been increased to **1.18** in order to not become outdated for a longer time.
+The minimum version of Go needed to compile Gitea has been increased to **1.18**.
 
 ### :exclamation: Changed handling of custom logo ([#18542](https://github.com/go-gitea/gitea/pull/18542))
 
@@ -172,21 +172,19 @@ If you use custom templates, check that they do not use `RequireHighlightJS` any
 
 ### :exclamation: Reserved usernames updated ([#18438](https://github.com/go-gitea/gitea/pull/18438))
 
-Reserved usernames are usernames that no user can ever have.  
-The following usernames are now reserved: `avatar`, `ssh_info`, and `swagger_v1.json`.  
+The following usernames are now newly reserved: `avatar`, `ssh_info`, and `swagger_v1.json`.  
 The following usernames are **no longer** reserved: `help`, `install`, `less`, `plugins`, `stars`, and `template`.
 
 If you want to check if you're affected, please run the following Gitea doctor command:
 ```
 gitea doctor --run check-user-name
 ```
-
 Note that this command is only available after upgrading to 1.17.0.
 
 ### :exclamation: Deprecated SSH ciphers removed from default setting ([#18697](https://github.com/go-gitea/gitea/pull/18697))
 
-This only affects Gitea instances that have enabled the internal SSH server.
-Previously, Gitea allowed unsecured algorithms to be used for an SSH connection.
+This only affects Gitea instances that have enabled the internal SSH server.  
+Previously, Gitea allowed unsecured algorithms to be used for an SSH connection.  
 Older versions of OpenSSH might not be able to connect to Gitea anymore.
 
 ### :exclamation: Display messages for users if the ROOT_URL is wrong, show JavaScript errors ([#18971](https://github.com/go-gitea/gitea/pull/18971))
@@ -208,8 +206,8 @@ All occurrences of such status code were now changed to `Temporary Redirect` (30
 
 ### :exclamation: No more admin notice about successful cron tasks ([#19221](https://github.com/go-gitea/gitea/pull/19221))
 
-Successful cron task no longer emit a notification by default.
-This breaks `NO_SUCCESS_NOTICE` settings.
+Successful cron task no longer emit a notification by default.  
+This breaks `NO_SUCCESS_NOTICE` settings.  
 If you want notices on success, you must set `NOTICE_ON_SUCCESS=true`.
 
 ## Changelog