fix(service): supabase studio fails to load schemas

[zenoUsman]

Changes

• Upgraded supabase studio to 2026.01.05-sha-1077b50
• fix(service): supabase studio fails to load schemas

[ShadowArcanist]

The CVE is already fixed by #7711 no?

[github-actions]

Hi @zenoUsman! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation

[zenoUsman]

The CVE is already fixed by #7711 no?

no the CVE still exist in 15.5.2 version according to article of next js, the current supabase studio on coolify runs on 15.5.2 the CVE fixed in 15.5.9 version and current version of official supabase studio image is running on 16.0.10 with cli version 2.67.1. so updating the image version needed to fix CVE.

[ShadowArcanist]

The CVE is already fixed by #7711 no?

no the CVE still exist in 15.5.2 version according to article of next js, the current supabase studio on coolify runs on 15.5.2 the CVE fixed in 15.5.9 version and current version of official supabase studio image is running on 16.0.10 with cli version 2.67.1. so updating the image version needed to fix CVE.

I just deployed a brand new supabase using the template we currently have at Coolify and studio is using "next": "^16.0.10", so the PR I mentioned on my previous comment actually patched the CVE with image: supabase/studio:2025.12.17-sha-43f4f7f.

[zenoUsman]

Okay mine when update to that version it's install 15.5.2 then I added latest version after that 16.0.10 appeared.

[zenoUsman]

Second problem without new two variables the supabase studio can't communicate with database which shows schema error when you visit supabase dashboard

[ShadowArcanist]

Okay mine when update to that version it's install 15.5.2 then I added latest version after that 16.0.10 appeared.

I again tried deploying supabase in a completely different Coolify instance using the service template and it was using Nextjs 16.0.10 so our current template is not vulnerable to react2shell CVE. You have updated the docker image tag to new version which is a good thing ^^

So this PR mainly fixes the issue with db schema!

[peaklabs-dev]

Thanks for the PR. I fixed this on next ccda7db.

Next time make sure variables are named the same and also that you do not open a PR from your v4.x branch.