To correspond with the ACM 2.5.1 zStream release, we'll need to version our CSV that ACM picks up.
Atm I don't think we have fixes destined for release-0.4.1 but we do need to version the CSV so that ACM 2.5.1 can publish a new version - this is because images will be re-spun to pickup fixes in the base ubi8 image (and possibly golang as well).
After this step is done, the ACM midstream will need to be modified to start picking up from the release-0.4 branch again instead of the hardcoded commit that corresponds with VolSync 0.4.0
To correspond with the ACM 2.5.1 zStream release, we'll need to version our CSV that ACM picks up.
Atm I don't think we have fixes destined for release-0.4.1 but we do need to version the CSV so that ACM 2.5.1 can publish a new version - this is because images will be re-spun to pickup fixes in the base ubi8 image (and possibly golang as well).
After this step is done, the ACM midstream will need to be modified to start picking up from the release-0.4 branch again instead of the hardcoded commit that corresponds with VolSync 0.4.0