[pull] master from supabase:master#906
Merged
Merged
Conversation
## Summary `apps/www/public/rss.xml` is committed to the repo AND rewritten on every `pnpm dev`, `pnpm build`, and `pnpm typecheck` run via `content:build` -> `apps/www/scripts/generateStaticContent.mjs`. Anyone working in `apps/www` (or running `pnpm typecheck` from the monorepo root) sees a phantom `M apps/www/public/rss.xml` in `git status` every session. Easy to accidentally commit, otherwise has to be repeatedly stashed. The sibling `changelog-rss.xml` (written by the same script) is already gitignored. This aligns the main blog rss with the same treatment. ## Changes - Add `/public/rss.xml` to `apps/www/.gitignore` (alongside the existing changelog-rss entries; renamed the section header from "Changelog generated feeds" to "Generated feeds" to reflect what it now covers). - `git rm --cached apps/www/public/rss.xml` so git stops tracking the file. The on-disk copy is preserved for local dev. ## Testing No behavior change — the file is still generated by `content:build` and served from `public/` at build time. - [x] `git check-ignore -v apps/www/public/rss.xml` resolves to `apps/www/.gitignore:36` - [x] `apps/www/public/rss.xml` still on disk after `git rm --cached` - [ ] On a fresh clone + `pnpm install + pnpm --filter www build`, the file regenerates and is served at `/rss.xml` on the resulting build (Vercel preview will confirm via deploy). ## Linear - fixes GROWTH-836 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated repository configuration to properly manage auto-generated files. [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45745) <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Summary Eliminates the Google Search Console "Missing field 'item' (in 'itemListElement')" critical error on 230 `/docs/guides/*` pages. The schema was emitting `ListItem`s without an `item` field for intermediate category nodes that lack a URL in the docs nav. Per [Google's spec](https://developers.google.com/search/docs/appearance/structured-data/breadcrumb), `item` is required on every BreadcrumbList position except the last leaf — so url-less items are filtered out instead. Also fixes a smaller quality gap surfaced during preview verification: the `auth` section root in `NavigationMenu.constants.ts` was missing a `url`, so auth trails were dropping the "Auth" breadcrumb level (`Docs > Guides > JSON Web Tokens (JWT) > Overview` instead of `Docs > Guides > Auth > JSON Web Tokens (JWT) > Overview`). Every other section root already has a `url`; auth was the lone outlier. ## Testing Tested locally via vitest (`pnpm --filter docs exec vitest run lib/json-ld.test.ts`): - [x] All-urls chain: every `itemListElement` has string `item` and `name` - [x] Leaf-url-mismatch: leaf uses `pathname` even when the chain leaf URL differs - [x] All-url-less chain: returns `null` - [x] Empty chain: returns `null` Tested on the preview deploy against 7 representative GSC-flagged paths: - [x] `/docs/guides/getting-started/ai-prompts` — 4 positions, 0 missing - [x] `/docs/guides/getting-started/ai-skills` — 4 positions, 0 missing - [x] `/docs/guides/auth/jwts` — 4 positions, 0 missing (after auth fix: includes "Auth") - [x] `/docs/guides/auth/social-login/auth-google` — 4 positions, 0 missing (after auth fix: includes "Auth") - [x] `/docs/guides/database/postgres-js` — 4 positions, 0 missing - [x] `/docs/guides/storage/quickstart` — 4 positions, 0 missing - [x] `/docs/guides/platform/migrating-within-supabase/dashboard-restore` — 5 positions, 0 missing Post-merge: - [ ] validator.schema.org against deployed URL: 0 errors - [ ] GSC "Validate fix" on the breadcrumb issue (1-2 week re-crawl window) ## Linear - fixes GROWTH-835 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved breadcrumb validation to filter incomplete entries and avoid broken documentation links. * Restored root link for the Auth navigation section so the Auth menu item now navigates to /guides/auth. * **Tests** * Added comprehensive tests covering breadcrumb generation and edge cases. * **Refactor** * Streamlined breadcrumb JSON‑LD schema generation for clearer output and maintainability. [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45744) <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Fixes logo so it makes use of currentColor <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Improved GitHub icon color compatibility to properly adapt across different UI contexts. [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45773) <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Summary Google Search Console flagged 4 "URL not allowed" errors on `sitemap_www.xml` — malformed URLs like `https://supabase.comdata/legal/terms/v1` (missing slash, non-existent path). The generator was globbing `data/**/*.mdx`, picking up the 4 content-source MDX files under `data/legal/` that are imported by `pages/terms.tsx` and `pages/enterprise-terms.tsx` but are not themselves routed. With no path replacement mapping `data/...` to a route and no leading slash, the URL template concatenated to garbage. The real `/terms` and `/enterprise-terms` URLs come from the `pages/*.tsx` glob and are unaffected. ## Changes - Remove `data/**/*.mdx` glob (and its companion `!data/*.mdx` exclude) from the sitemap generator. `apps/www/data/` has no routed MDX, only content sources imported into pages. - Anchor the `pages` prefix replace: `.replace('pages', '')` → `.replace(/^pages/, '')`. String-form replace is first-occurrence and would mangle any future filename containing `pages` as a non-prefix substring (e.g., `_blog/about-pages.mdx` → `/blog/about-`). No current files trigger this; defensive hardening. ## Testing Regenerated the sitemap locally and verified: - [x] `grep -c "supabase.comdata" public/sitemap_www.xml` → `0` (was 4) - [x] `<loc>https://supabase.com/terms</loc>` and `<loc>https://supabase.com/enterprise-terms</loc>` still present - [x] Every `<loc>` matches `^<loc>https://supabase\.com(/[a-zA-Z0-9].*)?</loc>$` (no malformed URLs of any kind) - [x] Total loc count stable across both commits (regression-free for the anchor change) Local count is lower than prod (527 vs 906) because `.next/server/pages/**` partner/expert/feature HTML globs only resolve after a full build — runs correctly via `postbuild` on Vercel. After deploy lands, resubmit `sitemap_www.xml` in Google Search Console to force a re-crawl (otherwise daily-ish). Expect status to flip from "4 errors" to "Success" and Discovered pages: 906 → 902. ## Linear - fixes GROWTH-837 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Chores** * Improved sitemap generation to properly index specific content sections (blog, case studies, customers, events, and alternatives) with refined route path processing for better search engine discoverability. [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45775) <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Studio builds get skipped in Vercel anyway, but be deliberate in skipping approval. We don't want forks to be able to have a studio deployment approved. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Optimized the deployment authorization process to skip unnecessary status checks, reducing processing overhead and improving deployment pipeline efficiency. [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45781) <!-- end of auto-generated comment: release notes by coderabbit.ai -->
As requested by storage team, was planned back in the day but never executed, so removing this for now as not planned in near future.
## Summary - Removes the `SupaIcon` component (inline Supabase SVG logo) from `LogsSidebarMenuV2.tsx` - Removes the `icon` prop from the Collections and Database operations sidebar items - Makes `icon` optional in `LogsSidebarItem` so the span is only rendered when an icon is provided Closes FE-3203 ## Test plan - [ ] Navigate to Logs & Analytics in Studio - [ ] Confirm Collections and Database operations sidebar items no longer show the Supabase logo - [ ] Confirm Saved Queries items still show the SQL editor icon (unaffected) 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Updated the logs sidebar component to make icon display optional. * Removed icons from sidebar items in the logs navigation to streamline the interface presentation. [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45787) <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45745){kind=link}
](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45744){kind=link}
](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45773){kind=link}
](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45775){kind=link}
](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45781){kind=link}
](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/45787){kind=link}
github-actions
Bot
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )