But if a new, say, 0.22.5 comes out when the latest build is at 0.23.2, the former won't have an image built since it will never have been released as latest.
We can update the new flow to trigger builds for patches on maintenance releases as well. This would be useful as then a Decidim instance maintainer could easily upgrade to the latest on the version they're at by simply swapping the maintenance images.
https://github.com/decidim/decidim/pull/6931
(under review)triggers the new docker build and publishing flow (#50)(under review as well)for the latest release.But if a new, say,
0.22.5
comes out when the latest build is at0.23.2
, the former won't have an image built since it will never have been released aslatest
.We can update the new flow to trigger builds for patches on maintenance releases as well. This would be useful as then a Decidim instance maintainer could easily upgrade to the latest on the version they're at by simply swapping the maintenance images.