aboutsummaryrefslogtreecommitdiffstats
path: root/.github/workflows/cron-licenses.yml
Commit message (Collapse)AuthorAgeFilesLines
* feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 ↵Rui Chen2023-12-211-1/+1
| | | | | | | | | | | | | | 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>
* Bump workflows in github actions (#27836)Chongyi Zheng2023-10-301-1/+1
| | | | All major version upgrades are related to using Node v20 as default runtime
* actions/setup-go use go-version-file (#27651)Yevhen Pavlov2023-10-171-1/+1
| | | | These changes will allow not to specify the version of go in every pipeline.
* Upgrading the actions/checkout@4 (#27096)puni98692023-09-161-1/+1
| | | | | | | as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
* Lock go to 1.21 on CI (#26433)silverwind2023-08-101-1/+1
| | | | | | | To prevent unwanted surprises with new minor versions of go, lock the version to minor version using [semver tilde syntax](https://github.com/npm/node-semver#tilde-ranges-123-12-1). We were already getting 1.21.0 since yesterday, so use that version now as minimum.
* Build nightly binaries with Actions (#25308)techknowlogick2023-06-161-0/+1
| | | Co-authored-by: silverwind <me@silverwind.io>
* Fix setup-go actions (#25167)silverwind2023-06-091-2/+3
| | | | | | | | | | | | | | | | | | 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.
* Don't run build and test if only docs changed (#24530)Lunny Xiao2023-05-161-1/+1
| | | Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* GitHub Actions cleanups (#24620)silverwind2023-05-111-9/+8
| | | | | | | | | | - Remove actions name where command is descriptive enough - Use kebab-case instead of snake-case for step names - Use shorter job names because to make PR checks more readable - Remove duplicate `checks-backend` --------- Co-authored-by: Yarden Shoham <git@yardenshoham.com>
* Use Actions for DB & E2E tests (#24494)techknowlogick2023-05-041-2/+2
| | | | | | | | | | following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
* on scheduletechknowlogick2023-04-251-1/+1
|
* switch to use Actions from drone for cron (#24314)techknowlogick2023-04-251-0/+28
Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.