From e55e3556cb7630ecfce38f5aeff67702fc7b63d4 Mon Sep 17 00:00:00 2001 From: kodster28 Date: Tue, 29 Sep 2026 15:39:10 -0500 Subject: [PATCH] chore: update a few more broken links in docs --- apps/docs/content/_partials/metrics_access.mdx | 2 +- .../database/connecting-to-postgres/serverless-drivers.mdx | 2 +- .../content/guides/database/extensions/wrappers/overview.mdx | 4 ++-- .../troubleshooting/database-error-saving-new-user-RU_EwB.mdx | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/apps/docs/content/_partials/metrics_access.mdx b/apps/docs/content/_partials/metrics_access.mdx index d6f9043c3c9..55dae4e6778 100644 --- a/apps/docs/content/_partials/metrics_access.mdx +++ b/apps/docs/content/_partials/metrics_access.mdx @@ -34,7 +34,7 @@ className="rounded-lg border border-foreground/10 bg-surface-100 text-foreground You can provision long-lived automation tokens in two ways: - Create an account access token once at [**Account Settings > Access Tokens**](/dashboard/account/tokens) and reuse it wherever you configure observability tooling. - - **Optional**: programmatically exchange an access token for project API keys via the [Management API](/docs/reference/api/management-projects-api-keys-retrieve). + - **Optional**: programmatically exchange an access token for project API keys via the [Management API](/docs/reference/api/v1-get-project-api-keys). ```bash # (Optional) Exchange an account access token for project API keys diff --git a/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx b/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx index 7ddc03b5775..7257bb0f77b 100644 --- a/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx +++ b/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx @@ -131,7 +131,7 @@ Cloudflare's Workers runtime also uses the [V8 engine](https://v8.dev/), but it ### Drivers [#cloudflare-workers-drivers] -- [supabase-js](https://developers.cloudflare.com/workers/databases/native-integrations/supabase/) +- [supabase-js](https://developers.cloudflare.com/workers/databases/third-party-integrations/supabase/) - [Postgres.js](https://github.com/porsager/postgres?tab=readme-ov-file#cloudflare-workers-support) - [node-postgres](https://developers.cloudflare.com/workers/tutorials/postgres/) diff --git a/apps/docs/content/guides/database/extensions/wrappers/overview.mdx b/apps/docs/content/guides/database/extensions/wrappers/overview.mdx index 867129be896..e462c4ec56d 100644 --- a/apps/docs/content/guides/database/extensions/wrappers/overview.mdx +++ b/apps/docs/content/guides/database/extensions/wrappers/overview.mdx @@ -131,7 +131,7 @@ This process can be taxing on your database if you are moving large amounts of d WebAssembly (Wasm) is a binary instruction format that enables high-performance execution of code on the web. Wrappers now includes a Wasm runtime, which provides a sandboxed execution environment, to run Wasm foreign data wrappers. Combined Wrappers with Wasm, developing and distributing new FDW becomes much easier and you can even build your own Wasm FDW and use it on Supabase platform. -To learn more about Wasm FDW, visit [Wrappers official documentation](https://supabase.github.io/wrappers/). +To learn more about Wasm FDW, visit [Wrappers official documentation](https://fdw.dev/). ## Security @@ -223,4 +223,4 @@ else console.log(data) ## Resources -- Official [`supabase/wrappers` documentation](https://supabase.github.io/wrappers/) +- Official [`supabase/wrappers` documentation](https://fdw.dev/) diff --git a/apps/docs/content/troubleshooting/database-error-saving-new-user-RU_EwB.mdx b/apps/docs/content/troubleshooting/database-error-saving-new-user-RU_EwB.mdx index 64a2d0b389c..81223f9be04 100644 --- a/apps/docs/content/troubleshooting/database-error-saving-new-user-RU_EwB.mdx +++ b/apps/docs/content/troubleshooting/database-error-saving-new-user-RU_EwB.mdx @@ -52,7 +52,7 @@ error finding user: sql: Scan error on column index 8, name "confirmation_token" **Cause:** -The `auth` schema is managed by Supabase and expects specific column formats. This error typically happens when users are inserted directly via SQL or using an AI tool that uses a direct SQL `INSERT`, rather than through the [Auth API](/docs/reference/javascript/auth-api). A direct insert can leave required columns as `NULL` when the Auth service expects an empty string. +The `auth` schema is managed by Supabase and expects specific column formats. This error typically happens when users are inserted directly via SQL or using an AI tool that uses a direct SQL `INSERT`, rather than through the [Auth API](/docs/reference/javascript/auth). A direct insert can leave required columns as `NULL` when the Auth service expects an empty string. **Fix:**