Skip to content

feat: drop alpha labels, deprecate adapters, pin doc imports to @1 - #185

Merged
mandarini merged 2 commits into
mainfrom
feat/stable-middleware-surface
Sep 30, 2026
Merged

mandarini merged 2 commits into
mainfrom
feat/stable-middleware-surface

Conversation

@mandarini

@mandarini mandarini commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

Prepares @supabase/server for @supabase/middleware 1.0.0.

  • Removes the alpha labels from the pipeline-entry form of withSupabase, the @supabase/server/middleware/* subpaths, and withOAuthProtectedResource, across README, docs, and tsdoc.
  • Marks the framework adapters deprecated in the README: removal on December 1, 2026, no new submissions, with a pointer to the bridges in examples/frameworks and the framework integration guide.
  • Pins the npm:@supabase/server imports in README, getting-started, and the skill file to @1.

Blocked by supabase/middleware#49. Once 1.0.0 is on npm, this branch also bumps the @supabase/middleware dependency to ^1.0.0 and the e2e Deno pin, then ships as 1.9.0.

@pkg-pr-new

pkg-pr-new Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@supabase/server@185

commit: c38fb87

@mandarini
mandarini marked this pull request as ready for review September 29, 2026 16:43
@mandarini
mandarini requested review from a team as code owners September 29, 2026 16:43
@mandarini
mandarini force-pushed the feat/stable-middleware-surface branch from ec361e9 to c38fb87 Compare September 30, 2026 09:43
@mandarini mandarini self-assigned this Sep 30, 2026
@mandarini
mandarini merged commit da3a60a into main Sep 30, 2026
9 of 10 checks passed
@mandarini
mandarini deleted the feat/stable-middleware-surface branch September 30, 2026 09:48
mandarini added a commit to supabase/supabase that referenced this pull request Oct 12, 2026
…51494)

## Problem

The server and middleware reference pages on supabase.com still carry
alpha labels that were dropped from the source partials weeks ago.
#51031 (Sep 30) removed the alpha wording from the partials and #51276
(Oct 5) added the adapter removal date, but neither change reached the
live site.

The reference build (`apps/docs/scripts/build-reference-content.ts`,
`writeNewMarkdownPartials`) copies a partial to
`docs/ref/<library>/<name>.mdx` only when that file does not exist, and
the page renderer reads from `docs/ref`. Once a page has been seeded,
later edits to the partial are never picked up. The three affected pages
were seeded before those PRs merged.

The UI library MCP page has the same stale wording: it says the
`pipeline` entry form of `withSupabase` is alpha and tracks
`@supabase/middleware` 0.x. Middleware is at 1.x and `@supabase/server`
dropped the alpha label in supabase/server#185.

Linear:
[SDK-2161](https://linear.app/supabase/issue/SDK-2161/remove-the-public-beta-designation-from-supabaseserver).
Companion package PR: supabase/server#192.

## Solution

Copy the current partial bodies over their rendered twins. The
frontmatter is identical in each pair, and the partials are left
untouched:

- `apps/docs/docs/ref/server/frameworks.mdx`: adapters are now described
as deprecated with the December 1, 2026 removal date, the Versions note
tells readers to add `@supabase/middleware` as a direct dependency, the
migration steps include `npm install @supabase/middleware`, and "The
entry form is alpha" is gone.
- `apps/docs/docs/ref/middleware/introduction.mdx`: the "Alpha"
admonition is gone.
- `apps/docs/docs/ref/middleware/usage-examples.mdx`: the entry form
note no longer says alpha.

Rewrite one paragraph in `apps/ui-library/content/docs/headless/mcp.mdx`
so it states the version requirement (`@supabase/server` 1.6.0 or later)
and that the nested form behaves the same, without the alpha or 0.x
claims.

After this PR each `docs/ref` file is byte-identical to its partial, so
`diff` between the two is empty.

## Preview links

| Site | Live | Preview | Search for |
| ---------- |
---------------------------------------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------------------------------------------------------------------------------------
| --------------------------------------- |
| Docs |
[/docs/reference/server/frameworks](https://supabase.com/docs/reference/server/frameworks)
|
[/docs/reference/server/frameworks](https://docs-git-docs-drop-stale-alpha-labels-supabase.vercel.app/docs/reference/server/frameworks)
| `December 1, 2026` |
| Docs |
[/docs/reference/middleware/introduction](https://supabase.com/docs/reference/middleware/introduction)
|
[/docs/reference/middleware/introduction](https://docs-git-docs-drop-stale-alpha-labels-supabase.vercel.app/docs/reference/middleware/introduction)
| `is in alpha` (live only) |
| Docs |
[/docs/reference/middleware/usage-examples](https://supabase.com/docs/reference/middleware/usage-examples)
|
[/docs/reference/middleware/usage-examples](https://docs-git-docs-drop-stale-alpha-labels-supabase.vercel.app/docs/reference/middleware/usage-examples)
| `The entry form of` |
| UI library |
[/ui/docs/headless/mcp](https://supabase.com/ui/docs/headless/mcp) |
[/ui/docs/headless/mcp](https://ui-library-git-docs-drop-stale-alpha-labels-supabase.vercel.app/ui/docs/headless/mcp)
| `Composing` |

## Review instructions

1. Open the live and preview links for the frameworks page side by side.
Search for `alpha`: present on live, absent on preview. Search for
`December 1, 2026`: absent on live, present on preview.
2. Open the middleware introduction. The "Alpha" caution box is gone on
preview.
3. Open the middleware usage examples and expand the CORS example
details. The entry form note reads "needs `@supabase/server` 1.6.0 or
later" with no alpha.
4. Open the UI library MCP page. The paragraph after the `whoami` note
states the version requirement and no longer mentions alpha or 0.x.
5. Optional, in a checkout: `diff
apps/docs/spec/reference/server/v1/partials/frameworks.mdx
apps/docs/docs/ref/server/frameworks.mdx` prints nothing. Same for the
two middleware pages.

## Checklist

Check all before review:

- [x] I have read
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
- [ ] If I wrote a new docs topic or edited an existing topic, I used
the `/write-the-docs` or `/edit-the-docs` skill, which applies the docs
[style
guide](https://github.com/supabase/supabase/tree/master/apps/docs/style-guide)

The docs text is copied verbatim from partials that already went through
review in #51031 and #51276. The one rewritten paragraph in the UI
library page follows the Supabase writing style guide.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants