The SHA for `docker/build-push-action@v7.2.0` was corrupted in both `tag.yaml` and `cron.yaml`.
**Corrupt:** `f9f3042f7e2789586610d7f5c8f03e5195baf` (substring `0d7f5c8f`)
**Correct:** `f9f3042f7e2789586610d6e8b85c8f03e5195baf` (substring `0d6e8b85` from `git ls-remote`)
Same mutation pattern as the `anothrNick/github-tag-action` SHA fixed in #19.
Affected workflows:
- `.gitea/workflows/tag.yaml` line 42
- `.gitea/workflows/cron.yaml` line 47
Fixes CI run #2437 job #6165.
The SHA for docker/build-push-action@v7.2.0 in tag.yaml and cron.yaml
was corrupted: 0d7f5c8f should be 0d6e8b85.
Correct SHA from git ls-remote refs/tags/v7.2.0:
f9f3042f7e2789586610d6e8b85c8f03e5195baf
Fixes CI run #2437 job #6165 (reference not found on docker/login-action
clone — likely cascade from the corrupted build-push-action SHA).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The SHA for
docker/build-push-action@v7.2.0was corrupted in bothtag.yamlandcron.yaml.Corrupt:
f9f3042f7e2789586610d7f5c8f03e5195baf(substring0d7f5c8f)Correct:
f9f3042f7e2789586610d6e8b85c8f03e5195baf(substring0d6e8b85fromgit ls-remote)Same mutation pattern as the
anothrNick/github-tag-actionSHA fixed in #19.Affected workflows:
.gitea/workflows/tag.yamlline 42.gitea/workflows/cron.yamlline 47Fixes CI run #2437 job #6165.