mirror of https://github.com/go-gitea/gitea.git
3c6aa8d3e1
The `setup-go` actions did not all have `check-latest` which means they use some cached version of go that currently still resolves to go1.20.4, as seen in a number of recent runs that currently fail at govulncheck because of it: ```` Run actions/setup-go@v4 Setup go version spec >=1.20 Attempting to resolve the latest version from the manifest... matching >=1.20... Resolved as '1.20.4' ```` Add the [check-latest](https://github.com/actions/setup-go#check-latest-version) option which should guarantee that this cache is skipped. |
||
|---|---|---|
| .. | ||
| cron-licenses.yml | ||
| cron-lock.yml | ||
| cron-translations.yml | ||
| files-changed.yml | ||
| pull-compliance.yml | ||
| pull-db-tests.yml | ||
| pull-docker-dryrun.yml | ||
| pull-e2e-tests.yml | ||