You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Always use the Go version specified in the go.mod
so the release is always built with the exact Go version specified in
go.mod.
* Drop packages:write permission
No images are pushed to GitHub Container Registry (ghcr.io).
* Get rid of Fossa scan during release
it is already executed for every relevant push action.
* Prepare Docker environment step should be obsolete
with GoReleaser Docker v2 engine.
* Improve release.yml readability
* Prepare GoReleaser for immutable releases
by using a draft gh release until the last step.
* Pin GoReleaser version to v2.14.3
* Pin tonistiigi/binfmt to a specific version
docker/setup-qemu-action defaults to tonistiigi/binfmt:latest, which
is a floating Docker Hub tag regardless of the action being SHA-pinned.
Pin to an explicit version tag and digest to prevent an attacker from
pushing a new :latest image between runs.
* Get rid of the manual release trigger
because it does not make sense with immutable releases. We have to use
forks to not pollute the repo with immutable testing tags.
* Replace in-release tests with CI check on tagged commit
Instead of re-running unit and integration tests inside the release
workflow, query the CI workflow result for the pr of the commit the
tag points to.
Hotfix commits are pushed directly to a branch without a PR.
When no merged PR is found for the tagged commit, verify the
CI workflow runs on that commit instead.
Hotfix branches follow the pattern *-hotfix-*. CI must run
on push so that the release workflow can verify the commit.
Release branches require PRs, making the push trigger there
redundant, so getting rid of it.
Reading PR and Commit CI results requires permissions pull-requests and
checks.
* Skip known-hosts check on push events
GITHUB_BASE_REF is empty on push events; the script exits
with a usage error. The known-hosts check is only meaningful
in a PR context where a base branch is defined. Also quote
the variable to satisfy shellcheck SC2086.
* Remove Rancher code freeze verification in release workflow
because we should be still able to release and if required, it should
be done inside of the release-against-rancher action.
0 commit comments