Repository navigation
fix(auth): prevent 404 when reauthorizing OAuth access - #34
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
|
Kilo Code Review could not run — your account is out of credits. Add credits or switch to a free model to enable reviews on this change. |
This branch was previously 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.
Reauthorization links on Submit and in the repository scaffold/link dialog were intercepted by the SvelteKit catch-all page, showing
404 — no page at /auth/githubinstead of starting OAuth. Mark all three links withdata-sveltekit-reloadso they reach the backend OAuth endpoint.Prepare patch release 0.25.1.
Validation: full workspace tests pass (645 API tests); frontend and API typechecks pass; lint and frontend production build pass. Browser reproduction confirmed that full navigation reaches the backend instead of the CMS fallback.