Loïc Dachary d5e104fef1 [CI] publish: allow pushing a release to an existing tag ... It is necessary to set the tag before uploading to a repository that does not already have it. But when it does, there is no need. This is the case for instance in the forgejo integration repository. It is however best to verify the SHA of the tag is as expected to not attempt to override a release associated with a different SHA, presumably from a previous run.		2023-02-17 08:09:05 +01:00
..
images	[DOCS] RELEASE-NOTES.md	2023-02-11 17:23:20 +01:00
woodpecker-build	[CI] publish: allow pushing a release to an existing tag	2023-02-17 08:09:05 +01:00
woodpecker-publish
binaries-pull-push-test.sh	[CI] publish: allow pushing a release to an existing tag	2023-02-17 08:09:05 +01:00
binaries-pull-push.sh	[CI] publish: allow pushing a release to an existing tag	2023-02-17 08:09:05 +01:00
container-images-pull-verify-push-test.sh
container-images-pull-verify-push.sh
Dockerfile
Dockerfile-rootless