1.4.x images were removed because there are breaking changes in 1.5 that make rolling back impossible without users having to manually clear the site data in their browser and lose all of their groups, filters, etc.
that assumes it was ever fully deployed and accessible to users. if the deployment itself is causing issues there is no risk in going back to an earlier version. communication about breaking changes should be in the release notes, not by making it significantly harder for people to roll back an unsuccessful deployment. it is also unlikely that you're going to prevent people from rolling back in most cases, as most deployments will be on plain old docker setups that will have the older image cached locally. our infrastructure does not have a persistent cache for older images, especially if a new deployment is scheduled on a different node.
it is certainly possible for us to build images ourselves or pin them to sha256 hashes, but it's a lot more effort overall compared to using prebuilt images.
if this is to be expected again in the future it's essentially saying that pre-built images are not a recommended deployment method if you don't want tesseract to be fully unavailable until you have sufficient time to fix any upgrade issues that might occur.
the codeberg over github mention seems a bit odd, as codeberg doesn't even have the git tags for 1.5 yet, let alone the releases.