mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Pedro RodriguesandOpenAI Codex
2303de33f5
## Problem `pnpm dev:www` ran `content:build`, whose final `fetchAgentSkills` step rewrote the committed skills index. ## Change Local development now runs the existing `content:build:core` generators and serves the committed index. Every WWW build still runs `content:build`, which runs the core generators followed by `fetchAgentSkills`. ```mermaid flowchart LR L[Local dev] --> C[content:build:core] C --> N[Next dev] I[Committed index] --> N B[Preview / production build] --> F[content:build] F --> C F --> A[fetchAgentSkills] R[Latest GitHub release] --> A A --> D[Next build] ``` Preview builds fall back to the committed index if fetching fails. Production builds fail rather than publish a stale index. The committed fallback is updated to v0.1.9. ## Test plan - `pnpm dev:www` leaves the index unchanged and serves it byte-for-byte - stale v0.1.8 fixture refreshes to v0.1.9 through the real fetch script - `pnpm --filter www test turbo-build.test.ts` - `pnpm --filter www typecheck` - `pnpm exec prettier --check apps/www/package.json apps/www/public/.well-known/agent-skills/index.json` - [x] I have read [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) Closes [AI-1275](https://linear.app/supabase/issue/AI-1275/running-pnpm-devwww-modifies-the-generated-agent-skills-index) Co-authored-by: OpenAI Codex <noreply@openai.com>
