mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 17:35:10 +03:00
Guilherme SouzaandClaude Sonnet 4.6
bc863816fb
## Summary Updates reference docs based on recent SDK changes. ## Changes analyzed | SDK | Repo | Commits | Latest tag | |-----|------|---------|------------| | js | supabase/supabase-js | \`16dd265...7a9b2e1\` | v2.103.3 | | kt | supabase-community/supabase-kt | \`a671b7a...2a6f456\` | 3.5.0 | | dart | supabase/supabase-flutter | \`e37539e...01551e3\` | — (dep bumps only) | | py | supabase/supabase-py | \`761d972...36cfcd0\` | v3.0.0a1 (dep bumps only) | | swift | supabase/supabase-swift | \`17261e9...b2bf858\` | v2.43.1 (dep bumps only) | | csharp | supabase-community/supabase-csharp | — | no new commits | ## Documentation updates ### `apps/docs/spec/supabase_js_v2.yml` - Added `strip-nulls` entry pointing to `@supabase/postgrest-js.PostgrestTransformBuilder.stripNulls` — new method in v2.103.0 that strips null values from JSON responses via the `nulls=stripped` PostgREST media type parameter. TypeScript enrichments already contain the full documentation. ### `apps/docs/spec/supabase_kt_v3.yml` - Added OAuth 2.1 client admin CRUD API (`admin.oauth.*`) — new in supabase-kt 3.5.0: `listClients`, `createClient`, `getClient`, `updateClient`, `deleteClient`, `regenerateClientSecret` - Marked `IDToken.Config.data` parameter as deprecated (deprecated upstream in supabase-kt); updated sign-in example to remove deprecated usage ### `apps/docs/spec/common-client-libs-sections.json` - Added `strip-nulls` entry to the Database → Using modifiers nav section - Added 6 `admin-oauth-*` entries to the Auth Admin → OAuth Admin nav section for the new Kotlin OAuth 2.1 methods --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added documentation for the `stripNulls` function to remove null values from database results. * Expanded OAuth Admin API documentation with 6 new endpoints for OAuth client management: list, get, create, update, delete, and secret regeneration. * Marked deprecated parameter in ID Token sign-in configuration. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 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.