Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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.
Summary
Make authentication, password recovery, and profile copy describe what the app actually does (audit CF16–21).
passwordResetEmailAvailablecapability, backed solely by the existing mail-enabled flag. Loading, failed checks, and disabled mail cannot submit the reset form. The reset mutation continues to return an account-neutral resultBefore → after
Validation
Final head:
94d238c4d8475439a0f569d05590d270f6ac69d9.f5ea2bfdf2037ace6ad50f6c3c7feaa9df0693d9. No integration commit was pushed.continue-on-errormasks acceptance checks. This supersedes the earlier local missing-native-binding,fs-extra, and plugin-resolution limitations.dd33611and this head, showing signup requirements and reset unavailable state. Actual Next pages, synthetic local GraphQL data, no production account or email actions.The ordinary checks on this independent branch still run the old main workflows and remain red. Review/merge #221 first, then update/recheck the feature branches; the clean integration result is not a claim that those old branch checks are green.
Rollout and review notes
Deploy backend before frontend for the new GraphQL capability. An older/unavailable backend safely disables email recovery and explains that availability could not be checked.
No password length/complexity policy, token format, hashing, account state, session revocation, rate limit, mail configuration, credential storage, or user account was changed. No registration, reset email, real sign-in, or paid generation was submitted during verification.
Production mail configuration was not inferred. The browser evidence uses a deployment-wide mail-disabled fixture; it is not a claim that production reset email is disabled.