You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the restructuring of the python environments, both the gotrue and supafunc python packages are being deprecated, in favor of supabase_auth and supabase_functions respectively.
gotrue 2.12.4 and supafunc 0.10.2 have both been published with no changes other than metadata changes, and including deprecation warnings when importing from them.
Warning
Please note that 2.12.3 is the last version where both gotrue and supabase_auth are the same, and they will diverge going forward. The same is valid for supafunc and supabase_functions version 0.10.1.
Package name changes: December 14, 2024 Deprecation Notice Issued: August 8, 2025
Why?
This name change has occurred in December 2024, in trying to keep name parity with the JavaScript libraries, but these old packages have been receiving the same updates through a script in the publishing workflow. As part of the python CI restructuring effort, it doesn't make sense to keep two versions of the same package around, and thus they're not going to receive patches anymore.
What You Need to Do
Change all package references from gotrue to supabase_auth, and supafunc to supabase_functions, in pyproject.toml, setup.py, or other package metadata formats, and change all direct imports from those libraries (from gotrue import ...) to importing from the new ones instead (from supabase_auth import ...).
supabase-py 2.18.1 will drop all usages of gotrue and supafunc from the main library. If you are using gotrue and supafunc directly as transitive dependencies, please prefer importing directly from supabase instead (see this comment for more info).
Warning
This is not going to be available for long, as feature differences are bound to occur sooner or later.
Thank you for your attention and continued support. If you have any questions, feel free to reach out through GitHub Discussions or our community channels.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As part of the restructuring of the python environments, both the
gotrueandsupafuncpython packages are being deprecated, in favor ofsupabase_authandsupabase_functionsrespectively.gotrue 2.12.4andsupafunc 0.10.2have both been published with no changes other than metadata changes, and including deprecation warnings when importing from them.Warning
Please note that
2.12.3is the last version where bothgotrueandsupabase_authare the same, and they will diverge going forward. The same is valid forsupafuncandsupabase_functionsversion0.10.1.Affected libraries
supabase-pygotruesupafuncTimeline
Package name changes: December 14, 2024
Deprecation Notice Issued: August 8, 2025
Why?
This name change has occurred in December 2024, in trying to keep name parity with the JavaScript libraries, but these old packages have been receiving the same updates through a script in the publishing workflow. As part of the python CI restructuring effort, it doesn't make sense to keep two versions of the same package around, and thus they're not going to receive patches anymore.
What You Need to Do
Change all package references from
gotruetosupabase_auth, andsupafunctosupabase_functions, inpyproject.toml,setup.py, or other package metadata formats, and change all direct imports from those libraries (from gotrue import ...) to importing from the new ones instead (from supabase_auth import ...).supabase-py 2.18.1will drop all usages ofgotrueandsupafuncfrom the main library. If you are usinggotrueandsupafuncdirectly as transitive dependencies, please prefer importing directly fromsupabaseinstead (see this comment for more info).Warning
This is not going to be available for long, as feature differences are bound to occur sooner or later.
Thank you for your attention and continued support. If you have any questions, feel free to reach out through GitHub Discussions or our community channels.
Beta Was this translation helpful? Give feedback.
All reactions