on master change, new images are pushed as docker-radical:$ARCH and docker-radicale:$ARCH-$VERSION
Consequences:
on master change, published images gets overwritten
release version (eg. 2.1.10.0) are not released as multi-arch images
This PR does
only push new images on tag (eg. new tag 2.1.10.0 pushed gives the multi-arch images being built and pushed)
Consequences:
no images get pushed with version exactly matching the version of radicale (we have 2.1.10.0, radicale have only 2.1.10 (the last digit in our version is an increment of the Docker image, no Radicale itself)
Currently:
Consequences:
This PR does
Consequences:
close #30