Guilherme SouzaandClaude Opus 4.6
32f70db13d
## Summary This PR updates documentation based on recent changes across multiple SDK repositories since the last run on 2026-01-22. ## Changes Analyzed | SDK | Repository | Commits | Latest Tag | |-----|-----------|---------|------------| | **js** | supabase/supabase-js | 40 | v2.95.4-canary.2 | | **dart** | supabase/supabase-flutter | 4 | - | | **py** | supabase/supabase-py | 12 | v2.28.0 | | **swift** | supabase/supabase-swift | 14 | v2.41.1 | | **kt** | supabase-community/supabase-kt | 36 | 3.3.0 | | **csharp** | supabase-community/supabase-csharp | 1 | v1.1.2 | ## Documentation Updates ### JavaScript SDK (`supabase_js_v2.yml`) - Added optional `jwt` parameter documentation to `mfa.getAuthenticatorAssuranceLevel()` - Added `timeout` and `urlLengthLimit` options to `PostgrestClient` constructor with example ### Kotlin SDK (`supabase_kt_v3.yml`) - Added new `getClaims()` API section with description, parameters, and 3 examples - Added `channel` parameter to OTP `signInWith` config for WhatsApp support - Added WhatsApp OTP sign-in example ### Python SDK (`supabase_py_v2.yml`) - Added `from_.list_v2()` method documentation with cursor-based pagination support - Includes `SearchV2Options` parameter documentation and pagination example - Added note about new User model fields (`is_sso_user`, `deleted_at`, `banned_until`) on `get_user` ### Swift SDK (`supabase_swift_v2.yml`) - Added breaking change note for `mfa.unenroll()`: response now uses `id` instead of `factorId` (since v2.41.1) ### Phone Login Guide (`phone-login.mdx`) - Added Kotlin WhatsApp OTP example to the sign-in section ### SDKs with no documentation updates needed - **Dart**: Only CI and realtime type-cast fix (no user-facing API changes) - **C#**: Only README badge fix ## Test plan - [ ] Verify YAML spec files parse correctly - [ ] Review rendered documentation for new sections - [ ] Confirm code examples match actual SDK APIs --- Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
Versioning
All tools have versioned docs, which are kept in separate folders. For example, the CLI has the following folders and files:
cli: the "next" release.cli_spec: contains the DocSpec for the "next" release (see below).cli_versioned_docs: a version of the documentation for every release (including the most current version).cli_versioned_sidebars: a version of the sidebar for every release (including the most current version).
When you release a new version of a tool, you should also release a new version of the docs. You can do this via the command line. For example, if you just released the CLI version 1.0.1:
npm run cli:version 1.0.1
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the developers' guide and contributing guide.