Conversation
Replace Nuxt 4 + @nuxt/content with Next.js 16 static export, shadcn/ui, Tailwind v4, next-intl, next-themes, and build-time Supabase fetch. BREAKING CHANGE: Nuxt app removed; use pnpm, `supabase start`, `pnpm run db:seed`, and `pnpm run dev`. Publish on `v*` tag uses prod Supabase (SUPABASE_DB_URL, SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY secrets). CI keeps local Supabase. Output is `out/` (not `.output/public`). npm lockfile removed. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 16 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (145)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Keep v2 implementation docs; main only had the planning snapshot from #147. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Lighthouse results
Updated automatically by CI. |
Latest full-page screenshot
|
Avoid ARG/ENV for SUPABASE_* so credentials do not persist in image layers and Docker scanner warnings clear. Update CI/publish workflows and compose; fix add-hosts and Percy Playwright import. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Silence supabase start output, pass BuildKit credentials via secret files with masking, and use 172.17.0.1 instead of host-gateway for buildx. Fix HU static export via direct ui-messages lookup for section labels. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
# [3.0.0](v2.14.0...v3.0.0) (2026-07-06) * feat!: rewrite CV site on Next.js, Supabase, and pnpm ([#148](#148)) ([534de64](534de64)) ### BREAKING CHANGES * Nuxt app removed; use pnpm, `supabase start`, `pnpm run db:seed`, and `pnpm run dev`. Publish on `v*` tag uses prod Supabase (SUPABASE_DB_URL, SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY secrets). CI keeps local Supabase. Output is `out/` (not `.output/public`). npm lockfile removed. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(docker): pass Supabase credentials via BuildKit secrets Avoid ARG/ENV for SUPABASE_* so credentials do not persist in image layers and Docker scanner warnings clear. Update CI/publish workflows and compose; fix add-hosts and Percy Playwright import. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(ci): harden secrets in logs and unblock Docker build Silence supabase start output, pass BuildKit credentials via secret files with masking, and use 172.17.0.1 instead of host-gateway for buildx. Fix HU static export via direct ui-messages lookup for section labels. Co-authored-by: Cursor <cursoragent@cursor.com>
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
1 participant
Summary
@nuxt/contentwith Next.js 16 static export, shadcn/ui, Tailwind v4, next-intl, and next-themes/+/huv*tag) uses prod secrets (SUPABASE_DB_URL,SUPABASE_URL,SUPABASE_PUBLISHABLE_KEY) + schema migrateDockerfile(in-container build + nginx gzip); deny-all.gitignore/.dockerignoreBREAKING CHANGE
main)v2)@nuxt/content/ YAML runtimepnpm run db:seed.output/publicout/npm run generatepnpm run buildnpm run devsupabase start+pnpm run db:seed+pnpm run devPublish requires GitHub Actions secrets (see
docs/projects/next-shadcn-supabase-rewrite/github-secrets.md). Prod seed before firstv*tag.Test plan
pnpm install,supabase start,pnpm run db:seed,pnpm run dev→/and/hupnpm run buildproducesout/with JSON-LD, sitemap, robots, llms.txtv*tag → migrate job + Pages + GHCR imagePost-merge (Phase 6)
pnpm run db:seedif not done yetMade with Cursor