fix: alternative route of getting latest Gitea version
Use a code.forgejo.org mirror instead of the GitHub API to not be subject to rate limiting.
This commit is contained in:
parent
8464d5cdef
commit
53375283d4
3 changed files with 44 additions and 2 deletions
|
|
@ -67,6 +67,11 @@ function migration_assert() {
|
|||
}
|
||||
|
||||
function test_gitea_upgrades() {
|
||||
local token="$1"
|
||||
GITEA_AUTHORIZATION_HEADER="Authorization: token $token"
|
||||
|
||||
run dependencies
|
||||
|
||||
local config=$UPGRADE_DIR/default-app.ini
|
||||
# The Forgejo target migration version must be 10.0 because it is the last supported.
|
||||
# https://forgejo.org/2024-12-gitea-compatibility/
|
||||
|
|
@ -104,5 +109,4 @@ function test_upgrades() {
|
|||
|
||||
run test_successful_upgrades
|
||||
run test_forgejo_pprof
|
||||
run test_gitea_upgrades
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue