As noted in #520 (comment), --prev-version is currently required in update-quarkus-images, meaning the command can only update existing entries in quarkus-mandrel-builder-image/mandrel.yaml. It cannot handle the case of adding a brand-new Mandrel release line (e.g., the first mandrel-26.0.x release) where there is no previous version to replace.
Current behavior:
--prev-version is required = true and the command replaces prevVersionTag strings in mandrel.yaml with the new version- If
versions.size() != prevVersions.size(), the command aborts
Proposed change:
- Make
--prev-version optional
- When
--prev-version is omitted for a given version, append a new image entry to mandrel.yaml instead of replacing an existing one
- When
--prev-version is provided, keep the current replace behavior
As noted in #520 (comment),
--prev-versionis currently required inupdate-quarkus-images, meaning the command can only update existing entries inquarkus-mandrel-builder-image/mandrel.yaml. It cannot handle the case of adding a brand-new Mandrel release line (e.g., the firstmandrel-26.0.xrelease) where there is no previous version to replace.Current behavior:
--prev-versionisrequired = trueand the command replacesprevVersionTagstrings inmandrel.yamlwith the new versionversions.size() != prevVersions.size(), the command abortsProposed change:
--prev-versionoptional--prev-versionis omitted for a given version, append a new image entry tomandrel.yamlinstead of replacing an existing one--prev-versionis provided, keep the current replace behavior