The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
docs: add cli global install note and correct user.new_email (#43151)
Vaibhav83864997bd1c
diff --git a/apps/docs/content/guides/auth/auth-hooks/send-email-hook.mdx b/apps/docs/content/guides/auth/auth-hooks/send-email-hook.mdxindex 23ff0a707bc..ac5a90549ef 100644--- a/apps/docs/content/guides/auth/auth-hooks/send-email-hook.mdx+++ b/apps/docs/content/guides/auth/auth-hooks/send-email-hook.mdx@@ -372,7 +372,7 @@ Email sending depends on two settings: Email Provider and Auth Hook status.When `email_action_type` is `email_change`, the hook payload can include one or two OTPs and their hashes. This depends on your [Secure Email Change](/dashboard/project/_/auth/providers?provider=Email) setting.-- Secure Email Change enabled: two OTPs are generated, one for the current email (`user.email`) and one for the new email (`user.email_new`). You must send two emails.+- Secure Email Change enabled: two OTPs are generated, one for the current email (`user.email`) and one for the new email (`user.new_email`). You must send two emails.- Secure Email Change disabled: only one OTP is generated for the new email. You send a single email.<Admonition type="caution" title="Counterintuitive field naming">@@ -380,7 +380,7 @@ When `email_action_type` is `email_change`, the hook payload can include one orThe token hash field names are reversed due to backward compatibility. Pay careful attention to which token/hash pair goes with which email address:- `token_hash_new` → use with the **current** email address (`user.email`) and `token`-- `token_hash` → use with the **new** email address (`user.email_new`) and `token_new`+- `token_hash` → use with the **new** email address (`user.new_email`) and `token_new`Do not assume the `_new` suffix refers to the new email address.@@ -391,7 +391,7 @@ Do not assume the `_new` suffix refers to the new email address.When Secure Email Change is enabled (both token/hash pairs present):- Send to **current** email address (`user.email`): use `token` with `token_hash_new`-- Send to **new** email address (`user.email_new`): use `token_new` with `token_hash`+- Send to **new** email address (`user.new_email`): use `token_new` with `token_hash`When Secure Email Change is **disabled** (only one token/hash pair present):diff --git a/apps/docs/content/guides/local-development/cli/getting-started.mdx b/apps/docs/content/guides/local-development/cli/getting-started.mdxindex 1597264bcd9..5cd643b37d6 100644--- a/apps/docs/content/guides/local-development/cli/getting-started.mdx+++ b/apps/docs/content/guides/local-development/cli/getting-started.mdx@@ -78,6 +78,12 @@ You can also install the CLI as dev dependency via [npm](https://www.npmjs.com/pnpm install supabase --save-dev```+<Admonition type="note">++Global installation using `npm install -g supabase` is not supported. For global CLI usage, install via [Homebrew](/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=macos), [Scoop](/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=windows), or the [standalone binary](/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=linux).++</Admonition>+</TabPanel></Tabs>