The nextcloud image release kept the same minor version, so it's not
directly visible if your server runs the updated image or not.
Releasing a new version here does a 'undeploy' and 'deploy', which
pulls the latest image.
The nextcloud image release kept the same minor version, so it's not
directly visible if your server runs the updated image or not.
Releasing a new version here does a 'undeploy' and 'deploy', which
pulls the latest image.
The nextcloud image release kept the same minor version, so it's not
directly visible if your server runs the updated image or not.
Releasing a new version here does a 'undeploy' and 'deploy', which
pulls the latest image.
ineiti
self-assigned this 2026-10-22 07:08:52 +00:00
ineiti
requested review from Ghost 2026-10-22 08:08:19 +00:00
So this should actually pull the latest image from the docker hub, EXCEPT if the lookup fails!
It would be nicest to pin to a digest, BUT abra doesn't handle digests!
@dannygroenewegen @amras any ideas/suggestions?
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 nextcloud image release kept the same minor version, so it's not
directly visible if your server runs the updated image or not.
Releasing a new version here does a 'undeploy' and 'deploy', which
pulls the latest image.
So this should actually pull the latest image from the docker hub, EXCEPT if the lookup fails!
It would be nicest to pin to a digest, BUT abra doesn't handle digests!
@dannygroenewegen @amras any ideas/suggestions?