While reviewing #174, @jpvillaisaza realized (see #174 (comment)) that I had accidentally removed the call to dropOldReleases when a successful release was deployed, so old releases weren't being deleted; despite of this, my PR did pass the CI checks. This made clear that we need to add a test to check for that, as this behavior is to be expected since by default no more than 5 releases should be preserved unless the user increases that with the keep_releases setting via config.
While reviewing #174, @jpvillaisaza realized (see #174 (comment)) that I had accidentally removed the call to
dropOldReleaseswhen a successful release was deployed, so old releases weren't being deleted; despite of this, my PR did pass the CI checks. This made clear that we need to add a test to check for that, as this behavior is to be expected since by default no more than 5 releases should be preserved unless the user increases that with thekeep_releasessetting via config.