Repository navigation
Restore production Supabase auth landing pages - #460
Open
Muawiya-contact wants to merge 2 commits into
Open
Muawiya-contact wants to merge 2 commits into
Muawiya-contact wants to merge 2 commits into
Conversation
✅ Deploy Preview for coding-moves-one-concept-review ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This branch has not been deployed
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.
Production cutover hotfix
The production Supabase API still returns HTTP 404 for the public
/confirmed,/reset-password, and/privacypaths after Railway was deleted. The installed production app sends new signup and recovery redirects to the Supabase API address, so these missing routes can strand new accounts and password resets. The Netlify review site's learner privacy link also points at a missing path.This PR restores the three public browser pages in the current production
mainEdge API, adds route tests, and points the review site's learner privacy link at the Supabase page. It contains no database migration, mobile update, worker change, content switch, or new native dependency. The same fixes and separate mobile privacy-link cleanup are proposed fordevelopin #459; this narrowmainhotfix avoids releasing #458 and its staging-only migrations prematurely.Verification
/healthand the reviewer website returned HTTP 200.mainbase./confirmed.After an approved merge
Use the protected Deploy Supabase API and worker to production workflow on the exact merged
maincommit. Confirm the two exact Edge URLs are allowed in production Supabase Auth. Check all three browser paths return HTML, then test fresh signup and recovery emails with an owner-controlled account. Set the Site URL fallback to the exact/functions/v1/api/confirmedaddress only after it is live. The worker code is unchanged and existing generation/refill gates stay as they are. This operational API deploy does not run the mobile Release workflow or publish an OTA.