lukaszraczylo f7ae4c042f ci(release): move the v1 tag onto the image pin commit ...

The release job moves the rolling v1 tag to the release commit. The
update-action-version job then pins action.yml to the new image in a
later commit. So v1 always pointed at a commit that pinned the
previous image, and "@v1" users ran the previous release.

The job now checks out the released commit, pushes the pin commit with
"git push origin HEAD:main", and moves v1 onto it after that push
succeeds. If main moved during the release, the push fails and v1
stays where it is. The job runs only for main, and a concurrency group
queues overlapping release runs.

Claude-Session: https://claude.ai/code/session_01Qq1gbqQek1Zjtofo4VDRdW

2026-09-25 19:35:52 +01:00

..

autoupdate.yaml

Update golang version

2026-07-15 09:38:29 +01:00

pr.yaml

Update golang version

2026-07-15 09:38:29 +01:00

release.yaml

ci(release): move the v1 tag onto the image pin commit

2026-09-25 19:35:52 +01:00

static.yml

Move to shared github actions and goreleaser

2025-12-07 15:11:16 +00:00