You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(backend): point lockUser() JSDoc to the Brute force protection page - #10745
The Clerk Dashboard is moving the user lockout settings from the Protections page to a new Brute force protection page at /~/protect/brute-force (clerk/dashboard#10728). This updates the lockUser() JSDoc to link to the new page.
The lockUser() reference page in the docs is generated from this JSDoc. clerk/clerk#3815 makes the same change to the generated copy. Without this PR, the next Typedoc refresh would revert it.
This changes only the comment; there is no runtime change.
Do not merge until the Dashboard stack (clerk/dashboard#10722 → #10725 → #10727 → #10728) is in production. Before then, the link points to a page that doesn't exist yet.
Checklist
pnpm test runs as expected. Not run: the change is to a doc comment only.
pnpm build runs as expected. Not run, for the same reason. The pre-commit hook couldn't start locally (pnpm 12 wasn't installable), so I ran its Prettier check by hand; it passed.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated: clerk/clerk#3815
The Dashboard moves the lockout settings from Protections to a new
Brute force protection page (/~/protect/brute-force).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No actionable comments were generated in the recent review.
Walkthrough
The lockUser() JSDoc link now points to the Dashboard’s Brute force protection page. A patch changeset records the documentation update. The method implementation is unchanged.
clerk/javascript#10395: Changed the lockUser() JSDoc link to the Protections Dashboard page; this PR updates it to the Brute force protection page.
Suggested reviewers:mwickett
Merge Risk: Minimal · up to c07b3
The link update has no runtime effect. Confirm the Dashboard page is deployed before merging, as planned.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly identifies the lockUser() JSDoc link update to the Brute force protection page.
Description check
The description explains the JSDoc link change, its destination, and that it does not change runtime behavior.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.)
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.
Included review availability: This review used your included allowance. 5 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 8 reviews per hour.
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
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.
Description
The Clerk Dashboard is moving the user lockout settings from the Protections page to a new Brute force protection page at
/~/protect/brute-force(clerk/dashboard#10728). This updates thelockUser()JSDoc to link to the new page.The
lockUser()reference page in the docs is generated from this JSDoc. clerk/clerk#3815 makes the same change to the generated copy. Without this PR, the next Typedoc refresh would revert it.This changes only the comment; there is no runtime change.
Do not merge until the Dashboard stack (clerk/dashboard#10722 → #10725 → #10727 → #10728) is in production. Before then, the link points to a page that doesn't exist yet.
Checklist
pnpm testruns as expected. Not run: the change is to a doc comment only.pnpm buildruns as expected. Not run, for the same reason. The pre-commit hook couldn't start locally (pnpm 12 wasn't installable), so I ran its Prettier check by hand; it passed.Type of change
Part of PROT-1263
🤖 Generated with Claude Code