snazy opened a new issue, #3747: URL: https://github.com/apache/polaris/issues/3747
### Is your feature request related to a problem? Please describe. The approach implemented by #3515 is a good and for the user experience necessary improvement. The added approach is however not suitable when there are multiple releases happening concurrently (e.g. a new release candidate from `main` plus another from `release/1.4.x`), as the last released version would "remove" the concurrent "open" releases from the Helm index. A safer approach is to _not_ overwrite the Helm index in the 4th workflow but rather update the existing one. In (pseudo) code it looks like this: ```bash # Download and unpack the released helm package # Download the current Helm index.yaml helm repo index . --merge index.yaml --url https://github.com/apache/polaris/releases/download/<helm-package-for-version> # Upload the updated Helm index.yaml ``` The above approach prevents downloading all old Helm packages, which will eventually be a lot, and an always growing number of releases. Although the eventually merged Helm index cannot be voted on, because it is created after the vote, it is probably not an issue, because the Helm index is a _convenience_ generated release artifact and not part of the source. ### Describe the solution you'd like _No response_ ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
