build(deps): bump @logto/client from 2.8.1 to 3.1.4

[dependabot]

Bumps @logto/client from 2.8.1 to 3.1.4.

Changelog

Sourced from @​logto/client's changelog.

3.1.4

Patch Changes

• Updated dependencies [1a57720]
  • @​logto/js@​6.1.0

3.1.3

Patch Changes

• Updated dependencies [3f8d42f]
  • @​logto/js@​6.0.0

3.1.2

Patch Changes

• Updated dependencies [049533f]
  • @​logto/js@​5.1.1

3.1.1

Patch Changes

• Updated dependencies [114be86]
  • @​logto/js@​5.1.0

3.1.0

Minor Changes

• b7f3d14: add new sign-in option to skip clearing cached tokens from storage on sign-in

  Example usage:

  await logtoClient.signIn({ redirectUri, clearTokens: false });

Patch Changes

• d0fc122: improve error messages in client SDK

3.0.4

Patch Changes

• d6a900c: bump dependencies for security update
• Updated dependencies [d6a900c]

... (truncated)

Commits

• ebe96c7 release: version packages
• 15b7ff4 release: version packages (#934)
• 207a3c8 release: version packages (#922)
• b7f3d14 feat(client): add new sign-in option to skip clearing tokens on sign-in (#932)
• d0fc122 refactor: throw more detailed error messages in client SDK (#919)
• c6a0469 release: version packages (#897)
• d6a900c chore: bump deps for security update (#915)
• 447017e chore: update vitest coverage
• 9d90ac5 fix: fix Mock type issue
• 56923b7 chore(deps): update dependency vitest to v2.1.9 [security]
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	sk-keygen@​0.1.0
	@​logto/​client@​2.8.1 ⏵ 3.1.4	+1		-1
	typescript@​5.9.2
	zod@​3.25.76
	redis@​4.7.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		vitest@1.0.1 has a Critical CVE. CVE: GHSA-9crc-q9x8-hgqq Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening (CRITICAL) Affected versions: >= 1.0.0 < 1.6.1; >= 2.0.0 < 2.1.9; >= 3.0.0 < 3.0.5; <= 0.0.125 Patched version: 1.6.1 From: ? → npm/@bravo68web/prettier-config@1.2.6 → npm/vitest@1.0.1 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vitest@1.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		safer-buffer@2.1.2 has Obfuscated code. Confidence: 0.94 Location: Package overview From: ? → npm/graphqurl@1.0.3 → npm/@graphql-codegen/cli@5.0.7 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report