mirror of
https://gitea.com/gitea/blog.git
synced 2024-06-02 02:21:25 +05:30
Rename \\\n -> \n and add 1.20.0 release image
Additionally add krita file to have a shared template to re-use
This commit is contained in:
delvh
delvh
parent
f4a992149e
commit
64aa950f26
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
date: 2023-07-14T10:00:00+02:00
|
||||
date: 2023-07-15T19:00:00+02:00
|
||||
authors:
|
||||
- "delvh"
|
||||
- "yardenshoham"
|
||||
|
|
@ -9,6 +9,7 @@ authors:
|
|||
title: "Gitea 1.20 is released"
|
||||
tags: ["release"]
|
||||
draft: false
|
||||
coverImage: /article-logo/1.20.0-release.webp
|
||||
---
|
||||
|
||||
Gitea 1.20.0 is now released.
|
||||
|
|
@ -30,17 +31,17 @@ The changes are sorted descending by what we deem most important for users and a
|
|||
|
||||
### :warning: Refactored scoped tokens mechanism ([#24767](https://github.com/go-gitea/gitea/pull/24767))
|
||||
<!-- Should we talk about security implications here, or down below in the new features? -->
|
||||
As will be described down below in more detail, the permissions for _Personal Access Tokens_ (PATs) have changed.\
|
||||
While we have migrated all old tokens to the new format as close as possible, there are edge cases where an old token now has more/less permissions than before as the two systems have a completely different design.\
|
||||
As will be described down below in more detail, the permissions for _Personal Access Tokens_ (PATs) have changed.
|
||||
While we have migrated all old tokens to the new format as close as possible, there are edge cases where an old token now has more/less permissions than before as the two systems have a completely different design.
|
||||
If that's the case for you, please consider regenerating your token to prevent API calls from failing or your token having a too broad scope.
|
||||
|
||||
|
||||
### :warning: Removed/changed config entries ([#25010](https://github.com/go-gitea/gitea/pull/25010), [#24958](https://github.com/go-gitea/gitea/pull/24958), [#24754](https://github.com/go-gitea/gitea/pull/24754), [#24628](https://github.com/go-gitea/gitea/pull/24628), [#24505](https://github.com/go-gitea/gitea/pull/24505), [#24430](https://github.com/go-gitea/gitea/pull/24430/files), [#24270](https://github.com/go-gitea/gitea/pull/24270), [#23798](https://github.com/go-gitea/gitea/pull/23798), [#23733](https://github.com/go-gitea/gitea/pull/23733), [#23333](https://github.com/go-gitea/gitea/pull/23333), [#25604](https://github.com/go-gitea/gitea/pull/25604))
|
||||
|
||||
- We've removed the service worker functionality as it didn't bring any noticeable benefit, mostly added bugs, and was disabled since 1.17 by default already.\
|
||||
- We've removed the service worker functionality as it didn't bring any noticeable benefit, mostly added bugs, and was disabled since 1.17 by default already.
|
||||
Removed config key: `[ui].USE_SERVICE_WORKER`
|
||||
|
||||
- The default value of `[server].LFS_HTTP_AUTH_EXPIRY` has been increased from `20m` to `24h`. \
|
||||
- The default value of `[server].LFS_HTTP_AUTH_EXPIRY` has been increased from `20m` to `24h`.
|
||||
If you want to use the previous value, please set the setting.
|
||||
|
||||
- As will be described below, you can now set any git config also in your `app.ini`.
|
||||
|
|
@ -48,9 +49,9 @@ As such, we removed the section `[git.reflog]` and its keys have been moved to t
|
|||
- `[git.reflog].ENABLED` → `[git.config].core.logAllRefUpdates`
|
||||
- `[git.reflog].EXPIRATION` → `[git.config].gc.reflogExpire`
|
||||
|
||||
- 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. \
|
||||
- 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 setting `[time].FORMAT` is no longer used
|
||||
|
|
@ -59,19 +60,19 @@ Additionally, some default values have changed in this section.
|
|||
|
||||
- The default value of `[server].SSH_KEYGEN_PATH` has changed from `ssh-keygen` to ` ` (empty), meaning that Gitea parses public keys by default itself rather than passing it to the system as previously.
|
||||
|
||||
- `[repository].DEFAULT_REPO_UNITS` and `[repository].DISABLED_REPO_UNITS` accepted the key `actions.actions` for a short time.\
|
||||
- `[repository].DEFAULT_REPO_UNITS` and `[repository].DISABLED_REPO_UNITS` accepted the key `actions.actions` for a short time.
|
||||
However, the correct key should be `repo.actions`.
|
||||
|
||||
- `[repository.editor].PREVIEWABLE_FILE_MODES` was buggy and didn't work.\
|
||||
- `[repository.editor].PREVIEWABLE_FILE_MODES` was buggy and didn't work.
|
||||
As such, it is now removed.
|
||||
|
||||
- `[actions].DEFAULT_ACTIONS_URL` could previously be set to any custom URLs like https://gitea.com or http://your-git-server, and the default value was https://gitea.com. But now, `DEFAULT_ACTIONS_URL` only supports `github` (https://github.com) or `self` (the root url of current Gitea instance), and the default value is `github`. This change was made to make action names globally resolvable in most cases.
|
||||
|
||||
### :warning: Publication of `README.md` in `.profile` repos ([#23260](https://github.com/go-gitea/gitea/pull/23260))
|
||||
|
||||
As will be discussed below in the new features, Gitea now displays user profile READMEs.\
|
||||
The displayed content is that of the `README.md` of a `.profile` repo.\
|
||||
If you already have a repo with that name, its `README.md` will be publically accessible, **even if the repo is private**.\
|
||||
As will be discussed below in the new features, Gitea now displays user profile READMEs.
|
||||
The displayed content is that of the `README.md` of a `.profile` repo.
|
||||
If you already have a repo with that name, its `README.md` will be publically accessible, **even if the repo is private**.
|
||||
If you don't want to leak that information, consider renaming your existing repo.
|
||||
|
||||
|
||||
|
|
@ -101,31 +102,31 @@ User and organization names can no longer end with `.png`.
|
|||
### :warning: Changed access log format ([#24085](https://github.com/go-gitea/gitea/pull/24085))
|
||||
|
||||
Logs from the access logger were previously escaped in unnecessary places.
|
||||
Now, they no longer are.\
|
||||
Now, they no longer are.
|
||||
Furthermore, the field `{{.Ctx.RemoteAddr}}` has been renamed to `{{.Ctx.RemoteHost}}` to omit the port.
|
||||
|
||||
### :warning: Correct pagination in API route `teams/{id}/members` ([#24754](https://github.com/go-gitea/gitea/pull/24754))
|
||||
|
||||
Previously, this endpoint was 0-based paginated unlike all other routes. \
|
||||
Previously, this endpoint was 0-based paginated unlike all other routes.
|
||||
This bug has now been fixed.
|
||||
|
||||
### :warning: Refactored path and config system ([#25416](https://github.com/go-gitea/gitea/pull/25416))
|
||||
|
||||
The Gitea path system has been fairly complicated for a long time:\
|
||||
It tried to guess paths quite often, which lead to countless problems.\
|
||||
Instead, Gitea now automatically tries to store the path inside the config.\
|
||||
The Gitea path system has been fairly complicated for a long time:
|
||||
It tried to guess paths quite often, which lead to countless problems.
|
||||
Instead, Gitea now automatically tries to store the path inside the config.
|
||||
If it fails to do so, it won't start. In that case, please do what the error message in the logs tells you to do and the issue should be resolved.
|
||||
|
||||
### :warning: `actions` table metrics collector was removed ([#25062](https://github.com/go-gitea/gitea/pull/25062))
|
||||
|
||||
The statistic of how many entries are in the `actions` table has always been rather useless as this table will always be (ridiculuously) large.\
|
||||
As such, we removed the metrics collector for it.\
|
||||
The statistic of how many entries are in the `actions` table has always been rather useless as this table will always be (ridiculuously) large.
|
||||
As such, we removed the metrics collector for it.
|
||||
Please do not rely on its output anymore.
|
||||
|
||||
### :warning: Rework storage settings ([#23911](https://github.com/go-gitea/gitea/pull/23911))
|
||||
|
||||
All storage settings should be stored in one section, and one section only.
|
||||
You cannot use multiple sections anymore to override settings.\
|
||||
You cannot use multiple sections anymore to override settings.
|
||||
The storage settings priority is now
|
||||
1. `[attachment]`
|
||||
2. `[storage.attachments]` | `[storage.<another>]`
|
||||
|
|
@ -137,8 +138,8 @@ The prioioty of the override configuration is `[attachment]` > `[storage.attachm
|
|||
|
||||
### :warning: Refactor ctx in templates ([#23105](https://github.com/go-gitea/gitea/pull/23105))
|
||||
|
||||
If you use custom templates, you may need to change them:\
|
||||
We've changed all occurring `.ctx` inside parameters to `.ctxData`.\
|
||||
If you use custom templates, you may need to change them:
|
||||
We've changed all occurring `.ctx` inside parameters to `.ctxData`.
|
||||
Any custom template currently using `.ctx` will need to follow suit.
|
||||
|
||||
### :warning: Rewrite logger system ([#24726](https://github.com/go-gitea/gitea/pull/24726))
|
||||
|
|
@ -191,8 +192,8 @@ So,
|
|||
|
||||
### :rocket: Gitea Actions
|
||||
|
||||
Gitea Actions has seen quite a number of new features since its initial launch in 1.19.0.\
|
||||
Nevertheless, it is still in an experimental state.\
|
||||
Gitea Actions has seen quite a number of new features since its initial launch in 1.19.0.
|
||||
Nevertheless, it is still in an experimental state.
|
||||
Here's what's new **on Gitea's side**:
|
||||
- Gitea no longer crashes on an invalid workflow file :smiley: ([#23972](https://github.com/go-gitea/gitea/pull/23972))
|
||||
- More available variables ([#24356T](https://github.com/go-gitea/gitea/pull/24356))
|
||||
|
|
@ -223,8 +224,8 @@ It is now possible to create an issue config by creating one of the files
|
|||
1. `.github/ISSUE_TEMPLATE/config.y(a)ml`
|
||||
1. `.github/issue_template/config.y(a)ml`
|
||||
|
||||
(the files are queried in exactly this prioritization order).\
|
||||
The issue config can be used to influence how users open issues.\
|
||||
(the files are queried in exactly this prioritization order).
|
||||
The issue config can be used to influence how users open issues.
|
||||
With it, you can force users to open issues from a template, or to display additional links, i.e. to nudge users to use another workflow such as sending an email to report security issues instead of reporting it publically.
|
||||
```yaml
|
||||
blank_issues_enabled: false
|
||||
|
|
@ -262,11 +263,11 @@ So, Gitea changed it to the following mechanism now:
|
|||
### :rocket: Scoped PAT rework ([#24767](https://github.com/go-gitea/gitea/pull/24767))
|
||||
|
||||
We noticed that the existing approach to create scoped _Personal Access Tokens_ (PATs) was pretty confusing, even if you've created one previously.
|
||||
Hence, we rewrote them so that they are much easier to use.\
|
||||
Hence, we rewrote them so that they are much easier to use.
|
||||
This is the new design:
|
||||
|
||||
|
||||
Meanwhile, this is the API page:\
|
||||
Meanwhile, this is the API page:
|
||||
|
||||
You can hopefully guess now what each of the new scopes mean.
|
||||
|
||||
|
|
@ -305,14 +306,14 @@ We now show the status of the latest commit of the default branch for each repos
|
|||
|
||||
### :rocket: Vertical instead of horizontal settings ([#24246](https://github.com/go-gitea/gitea/pull/24246))
|
||||
|
||||
We ran out of space to add new settings categories:\
|
||||
It is not usable if you need to scroll endlessly to find a category.\
|
||||
We ran out of space to add new settings categories:
|
||||
It is not usable if you need to scroll endlessly to find a category.
|
||||
Hence, we switched the settings order around, so that the settings categories are now displayed on the left instead of at the top:
|
||||
|
||||
|
||||
### :rocket: Expand/collapse all files of a PR ([#23639](https://github.com/go-gitea/gitea/pull/23639))
|
||||
|
||||
When reviewing the files of a PR, it is now possible to show or hide all changes.\
|
||||
When reviewing the files of a PR, it is now possible to show or hide all changes.
|
||||
This is especially useful when revisiting a PR you already reviewed to look for something.
|
||||
|
||||
|
||||
|
|
@ -355,17 +356,17 @@ If a protected branch requires status checks to pass before merging, the require
|
|||
|
||||
### :rocket: Systemd-notify support ([#21151](https://github.com/go-gitea/gitea/pull/21151))
|
||||
|
||||
Gitea can now notify `systemd` whenever it is ready.\
|
||||
To enable it, your systemd service file should contain the key `[Service].Type=notify`,\
|
||||
Gitea can now notify `systemd` whenever it is ready.
|
||||
To enable it, your systemd service file should contain the key `[Service].Type=notify`,
|
||||
as you can see for example in the [provided example file](https://github.com/go-gitea/gitea/blob/main/contrib/systemd/gitea.service).
|
||||
|
||||
Sidenote: We are aware that we should only have updated the [example file](https://github.com/go-gitea/gitea/blob/main/contrib/systemd/gitea.service) once the release was released.\
|
||||
Many people complained that systemd keeps restarting their (pre-1.20.0) Gitea after a few seconds as it expected status reports which previous Gitea versions obviously couldn't do.\
|
||||
Sidenote: We are aware that we should only have updated the [example file](https://github.com/go-gitea/gitea/blob/main/contrib/systemd/gitea.service) once the release was released.
|
||||
Many people complained that systemd keeps restarting their (pre-1.20.0) Gitea after a few seconds as it expected status reports which previous Gitea versions obviously couldn't do.
|
||||
Apologies for any headaches this may have caused.
|
||||
|
||||
### :rocket: Configure Git through your `app.ini` ([#24860](https://github.com/go-gitea/gitea/pull/24860))
|
||||
|
||||
Any entries in your`app.ini` in the `[git.config]` section will now be used to customize the git internal behavior for Gitea.\
|
||||
Any entries in your`app.ini` in the `[git.config]` section will now be used to customize the git internal behavior for Gitea.
|
||||
In other words,
|
||||
```ini
|
||||
[git.config]
|
||||
|
|
@ -377,7 +378,7 @@ is equal to
|
|||
git config a.key value1;
|
||||
git config b.key value2;
|
||||
```
|
||||
for the gitconfig used by Gitea.\
|
||||
for the gitconfig used by Gitea.
|
||||
This has the following benefits:
|
||||
1. Gitea can set all options it needs itself
|
||||
2. All config options declared in the config cheatsheet and example app.ini are values that Gitea will set itself if not overridden
|
||||
|
|
|
|||
BIN
static/article-logo/1.20.0-release-krita-file.kra
Normal file
BIN
static/article-logo/1.20.0-release-krita-file.kra
Normal file
Binary file not shown.
BIN
static/article-logo/1.20.0-release.webp
Normal file
BIN
static/article-logo/1.20.0-release.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Loading…
Reference in a new issue