loading up the forgejo repo on tangled to test page performance
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565)
Update more actions to use nodejs20 runtime and also update the docs for
checkout action usage.
similar to:
- #27836
- #27096
---------
Signed-off-by: Rui Chen <rui@chenrui.dev>
+46
-46
+1
-1
.github/workflows/cron-licenses.yml
+1
-1
.github/workflows/cron-licenses.yml
+1
-1
.github/workflows/cron-lock.yml
+1
-1
.github/workflows/cron-lock.yml
+6
-6
.github/workflows/pull-compliance.yml
+6
-6
.github/workflows/pull-compliance.yml
···
17
17
runs-on: ubuntu-latest
18
18
steps:
19
19
- uses: actions/checkout@v4
20
-
- uses: actions/setup-go@v4
20
+
- uses: actions/setup-go@v5
21
21
with:
22
22
go-version-file: go.mod
23
23
check-latest: true
···
70
70
runs-on: ubuntu-latest
71
71
steps:
72
72
- uses: actions/checkout@v4
73
-
- uses: actions/setup-go@v4
73
+
- uses: actions/setup-go@v5
74
74
with:
75
75
go-version-file: go.mod
76
76
check-latest: true
···
87
87
runs-on: ubuntu-latest
88
88
steps:
89
89
- uses: actions/checkout@v4
90
-
- uses: actions/setup-go@v4
90
+
- uses: actions/setup-go@v5
91
91
with:
92
92
go-version-file: go.mod
93
93
check-latest: true
···
102
102
runs-on: ubuntu-latest
103
103
steps:
104
104
- uses: actions/checkout@v4
105
-
- uses: actions/setup-go@v4
105
+
- uses: actions/setup-go@v5
106
106
with:
107
107
go-version-file: go.mod
108
108
check-latest: true
···
130
130
runs-on: ubuntu-latest
131
131
steps:
132
132
- uses: actions/checkout@v4
133
-
- uses: actions/setup-go@v4
133
+
- uses: actions/setup-go@v5
134
134
with:
135
135
go-version-file: go.mod
136
136
check-latest: true
···
175
175
runs-on: ubuntu-latest
176
176
steps:
177
177
- uses: actions/checkout@v4
178
-
- uses: actions/setup-go@v4
178
+
- uses: actions/setup-go@v5
179
179
with:
180
180
go-version-file: go.mod
181
181
check-latest: true
+5
-5
.github/workflows/pull-db-tests.yml
+5
-5
.github/workflows/pull-db-tests.yml
···
39
39
- "9000:9000"
40
40
steps:
41
41
- uses: actions/checkout@v4
42
-
- uses: actions/setup-go@v4
42
+
- uses: actions/setup-go@v5
43
43
with:
44
44
go-version-file: go.mod
45
45
check-latest: true
···
64
64
runs-on: ubuntu-latest
65
65
steps:
66
66
- uses: actions/checkout@v4
67
-
- uses: actions/setup-go@v4
67
+
- uses: actions/setup-go@v5
68
68
with:
69
69
go-version-file: go.mod
70
70
check-latest: true
···
115
115
- "9000:9000"
116
116
steps:
117
117
- uses: actions/checkout@v4
118
-
- uses: actions/setup-go@v4
118
+
- uses: actions/setup-go@v5
119
119
with:
120
120
go-version-file: go.mod
121
121
check-latest: true
···
165
165
- "993:993"
166
166
steps:
167
167
- uses: actions/checkout@v4
168
-
- uses: actions/setup-go@v4
168
+
- uses: actions/setup-go@v5
169
169
with:
170
170
go-version-file: go.mod
171
171
check-latest: true
···
198
198
- "1433:1433"
199
199
steps:
200
200
- uses: actions/checkout@v4
201
-
- uses: actions/setup-go@v4
201
+
- uses: actions/setup-go@v5
202
202
with:
203
203
go-version-file: go.mod
204
204
check-latest: true
+1
-1
.github/workflows/pull-e2e-tests.yml
+1
-1
.github/workflows/pull-e2e-tests.yml
+3
-3
.github/workflows/release-nightly.yml
+3
-3
.github/workflows/release-nightly.yml
···
18
18
# fetch all commits instead of only the last as some branches are long lived and could have many between versions
19
19
# fetch all tags to ensure that "git describe" reports expected Gitea version, eg. v1.21.0-dev-1-g1234567
20
20
- run: git fetch --unshallow --quiet --tags --force
21
-
- uses: actions/setup-go@v4
21
+
- uses: actions/setup-go@v5
22
22
with:
23
23
go-version-file: go.mod
24
24
check-latest: true
···
64
64
# fetch all commits instead of only the last as some branches are long lived and could have many between versions
65
65
# fetch all tags to ensure that "git describe" reports expected Gitea version, eg. v1.21.0-dev-1-g1234567
66
66
- run: git fetch --unshallow --quiet --tags --force
67
-
- uses: actions/setup-go@v4
67
+
- uses: actions/setup-go@v5
68
68
with:
69
69
go-version-file: go.mod
70
70
check-latest: true
···
101
101
# fetch all commits instead of only the last as some branches are long lived and could have many between versions
102
102
# fetch all tags to ensure that "git describe" reports expected Gitea version, eg. v1.21.0-dev-1-g1234567
103
103
- run: git fetch --unshallow --quiet --tags --force
104
-
- uses: actions/setup-go@v4
104
+
- uses: actions/setup-go@v5
105
105
with:
106
106
go-version-file: go.mod
107
107
check-latest: true
+1
-1
.github/workflows/release-tag-rc.yml
+1
-1
.github/workflows/release-tag-rc.yml
···
17
17
# fetch all commits instead of only the last as some branches are long lived and could have many between versions
18
18
# fetch all tags to ensure that "git describe" reports expected Gitea version, eg. v1.21.0-dev-1-g1234567
19
19
- run: git fetch --unshallow --quiet --tags --force
20
-
- uses: actions/setup-go@v4
20
+
- uses: actions/setup-go@v5
21
21
with:
22
22
go-version-file: go.mod
23
23
check-latest: true
+1
-1
.github/workflows/release-tag-version.yml
+1
-1
.github/workflows/release-tag-version.yml
···
19
19
# fetch all commits instead of only the last as some branches are long lived and could have many between versions
20
20
# fetch all tags to ensure that "git describe" reports expected Gitea version, eg. v1.21.0-dev-1-g1234567
21
21
- run: git fetch --unshallow --quiet --tags --force
22
-
- uses: actions/setup-go@v4
22
+
- uses: actions/setup-go@v5
23
23
with:
24
24
go-version-file: go.mod
25
25
check-latest: true
+3
-3
docs/content/administration/config-cheat-sheet.en-us.md
+3
-3
docs/content/administration/config-cheat-sheet.en-us.md
···
1399
1399
- `SKIP_WORKFLOW_STRINGS`: **[skip ci],[ci skip],[no ci],[skip actions],[actions skip]**: Strings committers can place inside a commit message to skip executing the corresponding actions workflow
1400
1400
1401
1401
`DEFAULT_ACTIONS_URL` indicates where the Gitea Actions runners should find the actions with relative path.
1402
-
For example, `uses: actions/checkout@v3` means `https://github.com/actions/checkout@v3` since the value of `DEFAULT_ACTIONS_URL` is `github`.
1403
-
And it can be changed to `self` to make it `root_url_of_your_gitea/actions/checkout@v3`.
1402
+
For example, `uses: actions/checkout@v4` means `https://github.com/actions/checkout@v4` since the value of `DEFAULT_ACTIONS_URL` is `github`.
1403
+
And it can be changed to `self` to make it `root_url_of_your_gitea/actions/checkout@v4`.
1404
1404
1405
1405
Please note that using `self` is not recommended for most cases, as it could make names globally ambiguous.
1406
1406
Additionally, it requires you to mirror all the actions you need to your Gitea instance, which may not be worth it.
···
1409
1409
In earlier versions (`<= 1.19`), `DEFAULT_ACTIONS_URL` could be set to any custom URLs like `https://gitea.com` or `http://your-git-server,https://gitea.com`, and the default value was `https://gitea.com`.
1410
1410
However, later updates removed those options, and now the only options are `github` and `self`, with the default value being `github`.
1411
1411
However, if you want to use actions from other git server, you can use a complete URL in `uses` field, it's supported by Gitea (but not GitHub).
1412
-
Like `uses: https://gitea.com/actions/checkout@v3` or `uses: http://your-git-server/actions/checkout@v3`.
1412
+
Like `uses: https://gitea.com/actions/checkout@v4` or `uses: http://your-git-server/actions/checkout@v4`.
1413
1413
1414
1414
## Other (`other`)
1415
1415
+3
-3
docs/content/administration/config-cheat-sheet.zh-cn.md
+3
-3
docs/content/administration/config-cheat-sheet.zh-cn.md
···
1335
1335
- `MINIO_BASE_PATH`: **actions_log/**：Minio存储桶上的基本路径，仅在`STORAGE_TYPE`为`minio`时可用。
1336
1336
1337
1337
`DEFAULT_ACTIONS_URL` 指示 Gitea 操作运行程序应该在哪里找到带有相对路径的操作。
1338
-
例如，`uses: actions/checkout@v3` 表示 `https://github.com/actions/checkout@v3`，因为 `DEFAULT_ACTIONS_URL` 的值为 `github`。
1339
-
它可以更改为 `self`，以使其成为 `root_url_of_your_gitea/actions/checkout@v3`。
1338
+
例如，`uses: actions/checkout@v4` 表示 `https://github.com/actions/checkout@v4`，因为 `DEFAULT_ACTIONS_URL` 的值为 `github`。
1339
+
它可以更改为 `self`，以使其成为 `root_url_of_your_gitea/actions/checkout@v4`。
1340
1340
1341
1341
请注意，对于大多数情况，不建议使用 `self`，因为它可能使名称在全局范围内产生歧义。
1342
1342
此外，它要求您将所有所需的操作镜像到您的 Gitea 实例，这可能不值得。
···
1345
1345
在早期版本（`<= 1.19`）中，`DEFAULT_ACTIONS_URL` 可以设置为任何自定义 URL，例如 `https://gitea.com` 或 `http://your-git-server,https://gitea.com`，默认值为 `https://gitea.com`。
1346
1346
然而，后来的更新删除了这些选项，现在唯一的选项是 `github` 和 `self`，默认值为 `github`。
1347
1347
但是，如果您想要使用其他 Git 服务器中的操作，您可以在 `uses` 字段中使用完整的 URL，Gitea 支持此功能（GitHub 不支持）。
1348
-
例如 `uses: https://gitea.com/actions/checkout@v3` 或 `uses: http://your-git-server/actions/checkout@v3`。
1348
+
例如 `uses: https://gitea.com/actions/checkout@v4` 或 `uses: http://your-git-server/actions/checkout@v4`。
1349
1349
1350
1350
## 其他 (`other`)
1351
1351
+3
-3
docs/content/usage/actions/comparison.en-us.md
+3
-3
docs/content/usage/actions/comparison.en-us.md
···
22
22
### Absolute action URLs
23
23
24
24
Gitea Actions supports defining actions via absolute URL, which means that you can use actions from any git repository.
25
-
Like `uses: https://github.com/actions/checkout@v3` or `uses: http://your_gitea.com/owner/repo@branch`.
25
+
Like `uses: https://github.com/actions/checkout@v4` or `uses: http://your_gitea.com/owner/repo@branch`.
26
26
27
27
### Actions written in Go
28
28
···
125
125
Previously (Pre 1.21.0), `[actions].DEFAULT_ACTIONS_URL` defaulted to `https://gitea.com`.
126
126
We have since restricted this option to only allow two values (`github` and `self`).
127
127
When set to `github`, the new default, Gitea will download non-fully-qualified actions from `https://github.com`.
128
-
For example, if you use `uses: actions/checkout@v3`, it will download the checkout repository from `https://github.com/actions/checkout.git`.
128
+
For example, if you use `uses: actions/checkout@v4`, it will download the checkout repository from `https://github.com/actions/checkout.git`.
129
129
130
-
If you want to download an action from another git hoster, you can use an absolute URL, e.g. `uses: https://gitea.com/actions/checkout@v3`.
130
+
If you want to download an action from another git hoster, you can use an absolute URL, e.g. `uses: https://gitea.com/actions/checkout@v4`.
131
131
132
132
If your Gitea instance is in an intranet or a restricted area, you can set the URL to `self` to only download actions from your own instance by default.
133
133
Of course, you can still use absolute URLs in workflows.
+4
-4
docs/content/usage/actions/comparison.zh-cn.md
+4
-4
docs/content/usage/actions/comparison.zh-cn.md
···
22
22
### Action URL绝对路径
23
23
24
24
Gitea Actions支持通过URL绝对路径定义actions，这意味着您可以使用来自任何Git存储库的Actions。
25
-
例如，`uses: https://github.com/actions/checkout@v3`或`uses: http://your_gitea.com/owner/repo@branch`。
25
+
例如，`uses: https://github.com/actions/checkout@v4`或`uses: http://your_gitea.com/owner/repo@branch`。
26
26
27
27
### 使用Go编写Actions
28
28
···
129
129
### 下载Actions
130
130
131
131
当 `[actions].DEFAULT_ACTIONS_URL` 保持默认值为 `github` 时，Gitea将会从 https://github.com 下载相对路径的actions。比如：
132
-
如果你使用 `uses: actions/checkout@v3`，Gitea将会从 https://github.com/actions/checkout.git 下载这个 actions 项目。
133
-
如果你想要从另外一个 Git服务下载actions，你只需要使用绝对URL `uses: https://gitea.com/actions/checkout@v3` 来下载。
132
+
如果你使用 `uses: actions/checkout@v4`，Gitea将会从 https://github.com/actions/checkout.git 下载这个 actions 项目。
133
+
如果你想要从另外一个 Git服务下载actions，你只需要使用绝对URL `uses: https://gitea.com/actions/checkout@v4` 来下载。
134
134
135
-
如果你的 Gitea 实例是部署在一个互联网限制的网络中，有可以使用绝对地址来下载 actions。你也可以讲配置项修改为 `[actions].DEFAULT_ACTIONS_URL = self`。这样所有的相对路径的actions引用，将不再会从 github.com 去下载，而会从这个 Gitea 实例自己的仓库中去下载。例如： `uses: actions/checkout@v3` 将会从 `[server].ROOT_URL`/actions/checkout.git 这个地址去下载 actions。
135
+
如果你的 Gitea 实例是部署在一个互联网限制的网络中，有可以使用绝对地址来下载 actions。你也可以讲配置项修改为 `[actions].DEFAULT_ACTIONS_URL = self`。这样所有的相对路径的actions引用，将不再会从 github.com 去下载，而会从这个 Gitea 实例自己的仓库中去下载。例如： `uses: actions/checkout@v4` 将会从 `[server].ROOT_URL`/actions/checkout.git 这个地址去下载 actions。
136
136
137
137
设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](administration/config-cheat-sheet.md#actions-actions)。
138
138
+3
-3
docs/content/usage/actions/design.en-us.md
+3
-3
docs/content/usage/actions/design.en-us.md
···
95
95
### Connection 2, job containers to Gitea instance
96
96
97
97
The job containers have different network namespaces than the runner, even if they are on the same machine.
98
-
They need to connect to Gitea to fetch codes if there is `actions/checkout@v3` in the workflow, for example.
98
+
They need to connect to Gitea to fetch codes if there is `actions/checkout@v4` in the workflow, for example.
99
99
Fetching code is not always necessary to run some jobs, but it is required in most cases.
100
100
101
101
If you use a loopback address to register a runner, the runner can connect to Gitea when it is on the same machine.
···
103
103
104
104
### Connection 3, act runner to internet
105
105
106
-
When you use some actions like `actions/checkout@v3`, the act runner downloads the scripts, not the job containers.
106
+
When you use some actions like `actions/checkout@v4`, the act runner downloads the scripts, not the job containers.
107
107
By default, it downloads from [gitea.com](http://gitea.com/), so it requires access to the internet.
108
108
It also downloads some docker images from Docker Hub by default, which also requires internet access.
109
109
···
116
116
117
117
### Connection 4, job containers to internet
118
118
119
-
When using actions such as `actions/setup-go@v4`, it may be necessary to download resources from the internet to set up the Go language environment in job containers.
119
+
When using actions such as `actions/setup-go@v5`, it may be necessary to download resources from the internet to set up the Go language environment in job containers.
120
120
Therefore, access to the internet is required for the successful completion of these actions.
121
121
122
122
However, it is optional as well.
+3
-3
docs/content/usage/actions/design.zh-cn.md
+3
-3
docs/content/usage/actions/design.zh-cn.md
···
96
96
### 连接 2，Job容器到Gitea实例
97
97
98
98
即使Job容器位于同一台机器上，它们的网络命名空间与Runner不同。
99
-
举个例子，如果工作流中包含 `actions/checkout@v3`，Job容器需要连接到Gitea来获取代码。
99
+
举个例子，如果工作流中包含 `actions/checkout@v4`，Job容器需要连接到Gitea来获取代码。
100
100
获取代码并不总是运行某些Job所必需的，但在大多数情况下是必需的。
101
101
102
102
如果您使用回环地址注册Runner，当Runner与Gitea在同一台机器上时，Runner可以连接到Gitea。
···
104
104
105
105
### 连接 3，act runner到互联网
106
106
107
-
当您使用诸如 `actions/checkout@v3` 的一些Actions时，act runner下载的是脚本，而不是Job容器。
107
+
当您使用诸如 `actions/checkout@v4` 的一些Actions时，act runner下载的是脚本，而不是Job容器。
108
108
默认情况下，它从[gitea.com](http://gitea.com/)下载，因此需要访问互联网。
109
109
它还默认从Docker Hub下载一些Docker镜像，这也需要互联网访问。
110
110
···
117
117
118
118
### 连接 4，Job容器到互联网
119
119
120
-
当使用诸如`actions/setup-go@v4`的Actions时，可能需要从互联网下载资源，以设置Job容器中的Go语言环境。
120
+
当使用诸如`actions/setup-go@v5`的Actions时，可能需要从互联网下载资源，以设置Job容器中的Go语言环境。
121
121
因此，成功完成这些Actions需要访问互联网。
122
122
123
123
然而，这也是可选的。
+2
-2
docs/content/usage/actions/faq.en-us.md
+2
-2
docs/content/usage/actions/faq.en-us.md
···
43
43
Not yet.
44
44
It is technically possible to implement, but we need to discuss whether it is necessary.
45
45
46
-
## Where will the runner download scripts when using actions such as `actions/checkout@v3`?
46
+
## Where will the runner download scripts when using actions such as `actions/checkout@v4`?
47
47
48
48
You may be aware that there are tens of thousands of [marketplace actions](https://github.com/marketplace?type=actions) in GitHub.
49
-
However, when you write `uses: actions/checkout@v3`, it actually downloads the scripts from [gitea.com/actions/checkout](http://gitea.com/actions/checkout) by default (not GitHub).
49
+
However, when you write `uses: actions/checkout@v4`, it actually downloads the scripts from [gitea.com/actions/checkout](http://gitea.com/actions/checkout) by default (not GitHub).
50
50
This is a mirror of [github.com/actions/checkout](http://github.com/actions/checkout), but it's impossible to mirror all of them.
51
51
That's why you may encounter failures when trying to use some actions that haven't been mirrored.
52
52
+2
-2
docs/content/usage/actions/faq.zh-cn.md
+2
-2
docs/content/usage/actions/faq.zh-cn.md
···
43
43
目前还不可以。
44
44
从技术上讲是可以实现的，但我们需要讨论是否有必要。
45
45
46
-
## 使用`actions/checkout@v3`等Actions时，Job容器会从何处下载脚本？
46
+
## 使用`actions/checkout@v4`等Actions时，Job容器会从何处下载脚本？
47
47
48
48
您可能知道GitHub上有成千上万个[Actions市场](https://github.com/marketplace?type=actions)。
49
-
然而，当您编写`uses: actions/checkout@v3`时，它实际上默认从[gitea.com/actions/checkout](http://gitea.com/actions/checkout)下载脚本（而不是从GitHub下载）。
49
+
然而，当您编写`uses: actions/checkout@v4`时，它实际上默认从[gitea.com/actions/checkout](http://gitea.com/actions/checkout)下载脚本（而不是从GitHub下载）。
50
50
这是[github.com/actions/checkout](http://github.com/actions/checkout)的镜像，但无法将它们全部镜像。
51
51
这就是为什么在尝试使用尚未镜像的某些Actions时可能会遇到失败的原因。
52
52
+1
-1
docs/content/usage/actions/overview.en-us.md
+1
-1
docs/content/usage/actions/overview.en-us.md
···
25
25
- "Gitea Actions" (with an "s", both words capitalized) is the name of the Gitea feature.
26
26
- "GitHub Actions" is the name of the GitHub feature.
27
27
- "Actions" could refer to either of the above, depending on the context. So it refers to "Gitea Actions" in this document.
28
-
- "action" or "actions" refer to some scripts/plugins to be used, like "actions/checkout@v3" or "actions/cache@v3".
28
+
- "action" or "actions" refer to some scripts/plugins to be used, like "actions/checkout@v4" or "actions/cache@v3".
29
29
30
30
## Runners
31
31
+1
-1
docs/content/usage/actions/overview.zh-cn.md
+1
-1
docs/content/usage/actions/overview.zh-cn.md
···
25
25
- "Gitea Actions"（两个单词都大写且带有"s"）是Gitea功能的名称。
26
26
- "GitHub Actions"是GitHub功能的名称。
27
27
- "Actions"根据上下文的不同可以指代以上任意一个。在本文档中指代的是"Gitea Actions"。
28
-
- "action"或"actions"指代一些要使用的脚本/插件，比如"actions/checkout@v3"或"actions/cache@v3"。
28
+
- "action"或"actions"指代一些要使用的脚本/插件，比如"actions/checkout@v4"或"actions/cache@v3"。
29
29
30
30
## Runner
31
31
+1
-1
docs/content/usage/actions/quickstart.en-us.md
+1
-1
docs/content/usage/actions/quickstart.en-us.md
···
113
113
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by Gitea!"
114
114
- run: echo "🔎 The name of your branch is ${{ gitea.ref }} and your repository is ${{ gitea.repository }}."
115
115
- name: Check out repository code
116
-
uses: actions/checkout@v3
116
+
uses: actions/checkout@v4
117
117
- run: echo "💡 The ${{ gitea.repository }} repository has been cloned to the runner."
118
118
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
119
119
- name: List files in the repository
+1
-1
docs/content/usage/actions/quickstart.zh-cn.md
+1
-1
docs/content/usage/actions/quickstart.zh-cn.md
···
112
112
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by Gitea!"
113
113
- run: echo "🔎 The name of your branch is ${{ gitea.ref }} and your repository is ${{ gitea.repository }}."
114
114
- name: Check out repository code
115
-
uses: actions/checkout@v3
115
+
uses: actions/checkout@v4
116
116
- run: echo "💡 The ${{ gitea.repository }} repository has been cloned to the runner."
117
117
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
118
118
- name: List files in the repository