Fix build reliability and harden admin integrations - #9
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
src/so admin protection is included in the production buildWhy
The repository could not perform a deterministic clean install, its build tooling failed before checking source, and the production home route returned 500 without configured Supabase variables. The admin middleware was not emitted from the existing location, leaving protected pages and database mutation endpoints reachable without the intended server-side guard. A Discord webhook credential was also committed directly in source.
Impact
Clean installs and production builds now complete. The public home page renders without service credentials, unauthenticated admin requests redirect to login, and privileged mutation APIs return 401 unless a verified administrator is present.
Validation
npm ci --dry-run --no-audit --no-fundnpm run lint(passes; 17 existing<img>optimization warnings)npx tsc --noEmitnpm run build/200,/admin/dashboard307 to login,/admin/login200POST /api/seed-certificatesandPOST /api/setup-db: 401Required follow-up
The previously committed Discord webhook must be revoked and regenerated because removing it from the current source does not remove it from Git history. Apply the hardened RLS policies to the live Supabase database and configure
ADMIN_EMAILplus the server-only variables documented in.env.example.