Why is Supabase applying silent migrations of future releases to my projects ??? This makes the systems unstable

[NisugaJ]

I am pretty sure the Supabase's silent migrations caused the authentication errors on our production app as It was perfectly working until last Monday(2024-03-18).
However, running silent DB migrations(of future releases) in production instances is not a good practice as it can fail systems like this.
Supabase should give an option in the admin dashboard to update the instances with migrations when the customer wants to apply the updates from Supabase (after the customer has tested the new Supabase updates in their test environments).

Hope that makes sense.

Thanks,
Nisuga

[NisugaJ]

Hereby, I request a feature to add an "Update project" button in the admin dashboard.
So the dev teams can apply the updates in their test project first, see whether it works well, and lastly on the production project.