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.
28 lines
810 B
YAML
28 lines
810 B
YAML
name: cron-licenses
|
|
|
|
on:
|
|
schedule:
|
|
- cron: "7 0 * * 1" # every Monday at 00:07 UTC
|
|
|
|
jobs:
|
|
cron-licenses:
|
|
runs-on: ubuntu-latest
|
|
if: github.repository == 'go-gitea/gitea'
|
|
steps:
|
|
- uses: actions/checkout@v3
|
|
- uses: actions/setup-go@v4
|
|
with:
|
|
go-version: ">=1.20"
|
|
check-latest: true
|
|
- run: make generate-license generate-gitignore
|
|
timeout-minutes: 40
|
|
- name: push translations to repo
|
|
uses: appleboy/git-push-action@v0.0.2
|
|
with:
|
|
author_email: "teabot@gitea.io"
|
|
author_name: GiteaBot
|
|
branch: main
|
|
commit: true
|
|
commit_message: "[skip ci] Updated licenses and gitignores"
|
|
remote: "git@github.com:go-gitea/gitea.git"
|
|
ssh_key: ${{ secrets.DEPLOY_KEY }}
|