chore(vue): Remove treatPendingAsSignedOut from useSession

[LauraBeatris]

Description

Leftover from #6432 - we've applied this change on the React hook but forgot to apply to Vue

Checklist

• pnpm test runs as expected.
• pnpm build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Summary by CodeRabbit

• Refactor
  • Simplified session state handling by removing the option to treat pending sessions as signed out.
  • Session status now consistently reflects a pending state when applicable, improving sign-in status accuracy.

[changeset-bot]

🦋 Changeset detected

Latest commit: defe17c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@clerk/vue	Patch
@clerk/nuxt	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
clerk-js-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2025 5:28pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes remove the treatPendingAsSignedOut option from the useSession hook in the @clerk/vue package. The function signature and its internal logic are updated to eliminate handling based on this option. The session state is now determined without considering pending sessions as signed out, and the isSignedIn flag directly reflects the value from the clerk context. Type definitions and imports related to the removed option are also deleted, simplifying the code.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a17a1e5 and defe17c.

📒 Files selected for processing (2)

• .changeset/sixty-dogs-film.md (1 hunks)
• packages/vue/src/composables/useSession.ts (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• .changeset/sixty-dogs-film.md

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/vue/src/composables/useSession.ts

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Formatting | Dedupe | Changeset
• GitHub Check: Build Packages
• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: semgrep/ci
• GitHub Check: Analyze (javascript-typescript)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[pkg-pr-new]

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6459

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6459

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6459

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6459

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6459

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6459

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6459

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6459

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6459

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6459

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6459

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6459

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6459

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6459

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6459

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6459

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6459

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6459

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6459

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6459

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6459

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6459

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6459

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6459

commit: defe17c

[wobsoriano]

🚀