Ah ok. I thought that we need an account to “link” to our repository. Good then.
Regards JB Le lun. 9 févr. 2026 à 13:17, Alexandre Dutra <[email protected]> a écrit : > Hi JB, > > I think with Artifact Hub the workflow is different: we don't need to > "push" anything to Artifact Hub during the release, so credentials are > not required at that moment. The chart stays hosted where it is today, > and Artifact Hub would "discover" it thanks to the chart annotations > and the artifacthub-repo.yml file. > > Thanks, > Alex > > On Mon, Feb 9, 2026 at 12:59 PM Jean-Baptiste Onofré <[email protected]> > wrote: > > > > Hi > > > > To be part of the automatic release, I guess we should ask infra to > create > > an account and give us via secret (as we do for DockerHub). > > It’s basically similar to what we do for DockerHub and PyPi (external > > resources from The ASF, ASF deals with Nexus and dist). > > > > Regards > > JB > > > > Le lun. 9 févr. 2026 à 11:37, Alexandre Dutra <[email protected]> a > écrit : > > > > > Hi all, > > > > > > A new PR is proposing to reference the Polaris Helm chart on Artifact > Hub > > > [1]. > > > > > > I think the idea is great, but since it requires some coordination and > > > changes to the release process, I thought it would be good to discuss > > > this idea here. > > > > > > The changes in the PR are just the first step. After that 2 more steps > > > would be required: > > > > > > 1) Registration: someone in the team must manually register the > > > Polaris Helm repository in Artifact Hub. > > > > > > 2) The semi-automated release scripts would need to be modified, > > > notably to copy the new artifacthub-repo.yml file to the Helm chart > > > repository root (at the same level as index.yaml). > > > > > > There might be more steps involved that I'm not aware of. > > > > > > What do you all think? Should we proceed with this? > > > > > > Thanks, > > > Alex > > > > > > [1]: https://github.com/apache/polaris/issues/3545 > > > >
