forgejo/.forgejo/workflows
Earl Warren ee7f568aed
fix(ci): do not block pull request CI when go-versions lags behind
When a new go version is published, it takes about 24h for
https://github.com/actions/go-versions to be updated (see
https://github.com/actions/go-versions/pull/102 for example).

In the meantime the setup-go action that depends on it will install a
version of go that fails golang.org/x/vuln/cmd/govulncheck.

Move the security check to be the last step of the test job instead of
the first. It will still block the PRs from being merged but it will
allow the PR authors to keep working and look at the test results in
the meantime.

Fixes: https://codeberg.org/forgejo/forgejo/issues/4294
2024-07-03 15:57:35 +02:00
..
backport.yml [CI] configure backport to comment on the PR on failure 2024-04-15 18:23:57 +02:00
build-release-integration.yml Disable duplicate builds 2024-03-25 13:24:53 +01:00
build-release.yml fix(release): add missing ARG RELEASE_VERSION 2024-04-17 17:16:53 +02:00
cascade-setup-end-to-end.yml [CI] simplify end-to-end test cascading PR 2024-03-20 18:16:56 +01:00
e2e.yml Revert "[CI] pin go v1.22.2 version" 2024-04-05 05:31:00 +02:00
mirror.yml [CI] mirror to forgejo-integration daily instead of each commit 2024-02-17 11:55:52 +01:00
publish-release.yml ci(release): upgrade v*.next.forgejo.org when the release is ready 2024-07-01 12:52:59 +02:00
renovate.yml Update renovate to v37.421.2 2024-07-01 00:01:26 +00:00
testing.yml fix(ci): do not block pull request CI when go-versions lags behind 2024-07-03 15:57:35 +02:00