diff options
| author | silverwind <me@silverwind.io> | 2023-06-09 09:33:48 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-09 09:33:48 +0200 |
| commit | 3c6aa8d3e19e2e558336e89aebc17d8adcf06350 (patch) | |
| tree | 6690fbf12f43dd15147135a9cb67bd41870aa43c /.github/workflows/cron-licenses.yml | |
| parent | 6d063a81f075d83fe41991b91fd175b100fdc0d5 (diff) | |
| download | gitea-3c6aa8d3e19e2e558336e89aebc17d8adcf06350.tar.gz gitea-3c6aa8d3e19e2e558336e89aebc17d8adcf06350.zip | |
Fix setup-go actions (#25167)
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.
Diffstat (limited to '.github/workflows/cron-licenses.yml')
| -rw-r--r-- | .github/workflows/cron-licenses.yml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/.github/workflows/cron-licenses.yml b/.github/workflows/cron-licenses.yml index 17b0d686d8..8642049117 100644 --- a/.github/workflows/cron-licenses.yml +++ b/.github/workflows/cron-licenses.yml @@ -10,9 +10,10 @@ jobs: if: github.repository == 'go-gitea/gitea' steps: - uses: actions/checkout@v3 - - uses: actions/setup-go@v3 + - uses: actions/setup-go@v4 with: - go-version: ">=1.20.1" + go-version: ">=1.20" + check-latest: true - run: make generate-license generate-gitignore timeout-minutes: 40 - name: push translations to repo |