Hi Adnan, Thanks for tackling the issues. I see that some fixes are on the release branch but I could not find them in a PR against the main branch.
It seems that CI is not happy with the release branch, any idea why? For better posterity, wouldn't it be better to use the standard pull-request workflow to push any changes to the release branches? Looks like something happened with the apache-polaris-1.4.0-rc0 Git tag. Wonder whether it has changed, because 'git fetch -t' complains with ` ! [rejected] apache-polaris-1.4.0-rc0 -> apache-polaris-1.4.0-rc0 (would clobber existing tag)`. Changing Git tags can easily lead to release verification issues. Robert On Wed, Mar 18, 2026 at 2:29 AM Adnan Hemani via dev <[email protected]> wrote: > Thanks Pierre! I also made another change, raised a PR for it, and > everything seems to be working with it. I'll manually verify the artifacts > and then send out the vote thread soon :) > > Best, > Adnan Hemani > > On Tue, Mar 17, 2026 at 3:14 AM Pierre Laporte <[email protected]> > wrote: > > > Hi Adnan, > > > > As JB mentioned, it seems that this issue happens because we have moved > > off of the incubator directory. There was indeed a bug in the workflow: > it > > implicitly required the `helm-chart` directory to exist. > > > > Note that, because the workflows are not idempotent, certain artifacts > > have already been published: > > * on dist dev: https://dist.apache.org/repos/dist/dev/polaris/1.4.0/ > > * on Nexus: the repo orgapachepolaris-1059 > > > > So you will have to perform a couple of manual cleanup operations before > > you can rerun this workflow: > > * delete the directory from dist dev > > * drop the Nexus repository > > > > Thanks for the quick fix ! > > > > -- > > > > Pierre > > > > > > On Tue, Mar 17, 2026 at 8:00 AM Jean-Baptiste Onofré <[email protected]> > > wrote: > > > >> Hi Adnan, > >> > >> I will take a look at this. It could be related to the transition from > >> dist/incubator/polaris to dist/polaris following graduation. > >> > >> I will keep you posted asap. > >> > >> Regards, > >> JB > >> > >> On Tue, Mar 17, 2026 at 12:57 AM Adnan Hemani via dev < > >> [email protected]> wrote: > >> > >> > Hi all, > >> > > >> > I opened https://github.com/apache/polaris/pull/4005 as a quick fix > >> based > >> > on my understanding of the issue I'm facing during release materials > >> > generation. Here's a quick rundown of the issue that I think I'm > facing > >> > (see GH PR link for the full error): > >> > > >> > I'm getting an SVN issue when trying to add the newly-generated Helm > >> charts > >> > to the Apache Polaris repo. My understanding is that this issue occurs > >> > because the `helm-chart` subdirectory isn't already added to the SVN > >> > repository. When comparing the 1.3.0-incubating release's workflow > [1], > >> the > >> > `helm-chart` subdirectory already existed, which is why we didn't see > >> this > >> > issue before. After moving out of the incubator, this subdirectory > >> doesn't > >> > pre-exist when running our release scripts. > >> > > >> > The underlying assumption I'm making as part of #4005 is that the > >> > `index.yml` file that already exists in the `helm-chart` subdirectory > in > >> > the incubator repo isn't important to pre-exist, as we re-generate > this > >> > file in the following step anyways. > >> > > >> > Can someone with more experience with the automated release system > >> comment > >> > if this is the right approach or if the `index.yml` is truly important > >> to > >> > have at this step in the release pipeline? > >> > > >> > Best, > >> > Adnan Hemani > >> > > >> > [1] > >> > > >> > > >> > https://github.com/apache/polaris/actions/runs/20854821902/job/59920537649#step:9:55 > >> > > >> > > >
