Hi Team,
We are using Supabase for our backend system, and I wanted to check if there is any existing versioning or rollback support for deployed Edge Functions.
For example, if we deploy a new version of an Edge Function and later need to revert to the previous stable version, is there a built-in way to roll back the deployment without manually redeploying the older code version again?
Thanks, Sunil
Sunil inquires about built-in versioning or rollback support for Supabase Edge Functions. Hardik K suggests that such a feature would be beneficial for production environments, highlighting the operational stress of manual rollbacks. An unknown user provides workarounds using Git and the Supabase CLI, noting the absence of native support. Sunil confirms they are using these methods but seeks a built-in solution.
This would be a very valuable feature for teams using Edge Functions in production.
Right now, rolling back typically means manually redeploying a previous commit/version from source control, which works, but can become operationally stressful during incidents where fast recovery matters.
Built-in deployment versioning + rollback support would provide several benefits:
A deployment history UI showing:
would already cover most real-world recovery workflows.
It could also be useful to support:
This becomes especially important for Edge Functions handling:
In those cases, a bad deployment can have immediate production impact, and “redeploy the old code manually” is not always ideal under pressure.
For now, the safest approach is probably:
Related references:
Definitely agree this would be a strong platform feature, especially as more teams use Supabase Edge Functions for production workloads rather than lightweight utility endpoints.
There's no built-in rollback or versioning for Edge Functions in Supabase currently. Here's what you can do instead:
Keep your Edge Functions in a git repo and use the Supabase CLI to deploy:
# Deploy current version
supabase functions deploy my-function
# Need to rollback? Checkout the previous commit and redeploy
git checkout HEAD~1 -- supabase/functions/my-function
supabase functions deploy my-function
2. CLI with tagged releases
Tag each deploy so you can easily revert:
git tag edge-v1.0 && git push --tags
# later...
git checkout edge-v1.0 -- supabase/functions/my-function
supabase functions deploy my-function
3. CI/CD pipeline
Set up GitHub Actions to auto-deploy on push and keep artifacts of each
version. The https://github.com/supabase/setup-cli makes this straightforward.
Supabase doesn't have a "rollback" button in the dashboard, but if you version
your functions in git and deploy via CLI, rolling back is just a git checkout
+ supabase functions deploy away.
There's an open feature request for native versioning — worth upvoting if you
want first-class support for this.
Yeah, we are already following that approach. I was checking whether Supabase has any built-in versioning or rollback feature to easily switch between Edge Function versions.