Superset new release 0.15.1 issue

[GMfragrnace]

Bug description

I am not seeing new release 0.15.1 in helm repo. I have newly added the repo and run repo update also. screenshot is attached for refference.

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hi @GMfragrnace! I'm Dosu and I’m helping the superset team.

The 0.15.1 Helm chart version was updated in the Superset codebase, but it hasn't been published to the official Helm repository yet, which is why you don't see it after running helm repo update details. This sometimes happens when the chart version bump is merged but the release process or automation hasn't published the chart to the repo example.

If you need 0.15.1 right away, you can clone the Superset repository and use the chart directly from the helm/superset directory to deploy that version how-to. Otherwise, once the chart is published, it will show up in the Helm repo after another helm repo update.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[GMfragrnace]

@dosu Is there any idea when will published the chart 0.15.1 as we are using through argocd by adding github repo of the version so we cannot use clone there. Regards, Ghulam Muhammad DevOps Engineer at M.M. Mobile : +92-33<https://wa.me/+923336286965>25274241 mercurialminds.com<https://mercurialminds.com/> Book a Time with ***@***.***?anonymous&ismsaljsauthenabled&ep=plink> | Connect on LinkedIn<https://www.linkedin.com/in/ghulamgma> M.M. is a collaborating firm of Andersen Consulting

…

________________________________ From: dosubot[bot] ***@***.***> Sent: Saturday, December 13, 2025 6:03 PM To: apache/superset ***@***.***> Cc: Ghulam Muhammad ***@***.***>; Mention ***@***.***> Subject: Re: [apache/superset] Superset new release 0.15.1 issue (Issue #36601) [https://avatars.githubusercontent.com/in/324583?s=20&v=4]dosubot[bot] left a comment (apache/superset#36601)<#36601 (comment)> Hi @GMfragrnace<https://github.com/GMfragrnace>! I'm Dosu<https://go.dosu.dev/dosubot> and I’m helping the superset team. The 0.15.1 Helm chart version was updated in the Superset codebase, but it hasn't been published to the official Helm repository yet, which is why you don't see it after running helm repo update details<#34327>. This sometimes happens when the chart version bump is merged but the release process or automation hasn't published the chart to the repo example<#34601>. If you need 0.15.1 right away, you can clone the Superset repository and use the chart directly from the helm/superset directory to deploy that version how-to<#35461>. Otherwise, once the chart is published, it will show up in the Helm repo after another helm repo update. To reply, just mention @dosu<https://go.dosu.dev/dosubot>.

________________________________ How did I do? Good<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=great_response> | Irrelevant<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=irrelevant_answer> | Incorrect<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=incorrect_sources> | Verbose<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=too_verbose> | Hallucination<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=hallucination> | Report 🐛<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=bug_report> | Other<https://app.dosu.dev/response-feedback/2aa3d8d0-468d-47e4-9b6b-1c26dac79056?feedback_type=other> [Chat with Dosu]<https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github> [Open in Cursor] <https://cursor.com/link/prompt?text=The%200.15.1%20Helm%20chart%20version%20was%20updated%20in%20the%20Superset%20codebase%2C%20but%20it%20hasn%27t%20been%20published%20to%20the%20official%20Helm%20repository%20yet%2C%20which%20is%20why%20you%20don%27t%20see%20it%20after%20running%20%60helm%20repo%20update%60%C2%A0%5Bdetails%5D%28https%3A//github.com/apache/superset/pull/34327%29.%20This%20sometimes%20happens%20when%20the%20chart%20version%20bump%20is%20merged%20but%20the%20release%20process%20or%20automation%20hasn%27t%20published%20the%20chart%20to%20the%20repo%C2%A0%5Bexample%5D%28https%3A//github.com/apache/superset/pull/34601%29.%0A%0AIf%20you%20need%200.15.1%20right%20away%2C%20you%20can%20clone%20the%20Superset%20repository%20and%20use%20the%20chart%20directly%20from%20the%20%60helm/superset%60%20directory%20to%20deploy%20that%20version%C2%A0%5Bhow-to%5D%28https%3A//github.com/apache/superset/issues/35461%29.%20Otherwise%2C%20once%20the%20chart%20is%20published%2C%20it%20will%20show%20up%20in%20the%20Helm%20repo%20after%20another%20%60helm%20repo%20update%60.> [Join Discord] <https://go.dosu.dev/discord-bot> [Share on X] <https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36601> — Reply to this email directly, view it on GitHub<#36601 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BB4E5ZYCJCGOWZ4ZNWNJPHL4BQFBNAVCNFSM6AAAAACO56OTK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBZGM4TEMRVGI>. You are receiving this because you were mentioned.Message ID: ***@***.***> [https://mercurialminds.com/MM-email-sig-2025-com.gif] <https://mercurialminds.com> Confidentiality Notice: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the organization. Finally, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.

[dosubot]

There’s no official ETA for when the Superset Helm chart 0.15.1 will be published to the Helm repository. The main blocker is that the chart is currently broken due to deprecated Bitnami dependencies for PostgreSQL and Redis, which complicates its release and usage. The chart is community-maintained, so new releases depend on community contributions and there’s no strict schedule for publication details.

For ArgoCD users who can’t use a local clone, the common workaround is to host the Helm chart files internally (for example, in a private Helm repo or a Git repository accessible to ArgoCD). This involves copying the chart from the Superset repo’s helm/superset directory, fixing any dependency references if needed, and serving it from your own infrastructure example. There’s no official alternative registry or migration path documented at this time.

If you need a published chart, you’ll need to monitor the repo for updates or consider this internal hosting approach until the official chart is fixed and published.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[sfirke]

Hi @GMfragrnace - looking at the releases listed, there is a helm chart there with the latest official release, 5.0.0. The fourth release candidate for becoming version 6.0.0 is up for a vote right now, 6.0.0rc4. You can follow the voting activity on the public superset-dev email list.

Until such a vote passes and 6.0.0 gets officially released, you are currently on the latest official release of Superset. Once 6.0.0 is out I hope someone will update the Helm chart; last I checked, there wasn't a single person responsible for that but it seems to typically happen.

[amrishparmar]

This is a duplicate of #35461

[sfirke]

Agreed @amrishparmar ! Thanks for flagging it, I'll close to focus the conversation.