fix(init): use @clerk/nuxt@latest now that keyless ships in stable

[rafa-thayto]

Summary

• Drop the sdkInstall: "@clerk/nuxt@2.2.0-snapshot.v20260413174426" override on the Nuxt entry in FRAMEWORK_MAP. The pin was a temporary bridge until keyless support landed in stable; the changelog confirms it shipped in @clerk/nuxt@2.2.0 ("Introduce Keyless quickstart for Nuxt"), and stable is now at 2.3.0.
• clerk init --starter for Nuxt now installs @clerk/nuxt@latest, matching every other framework in the registry.
• The generic sdkInstall field on FrameworkInfo stays as an escape hatch for future pinning.

Test plan

• bun run format / bun run lint / bun run typecheck
• bun test for framework.test.ts and commands/init/ (281 pass)
• Manual: run clerk init --starter against a fresh Nuxt project, confirm dev server boots and the keyless flow renders sign-in/sign-up

[changeset-bot]

🦋 Changeset detected

Latest commit: e0464af

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

[coderabbitai]

Warning

Rate limit exceeded

@rafa-thayto has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 40 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5ae40603-bf40-4c40-bdae-4d82f1e588c2

📥 Commits

Reviewing files that changed from the base of the PR and between 2ce88f7 and e0464af.

📒 Files selected for processing (2)

• .changeset/nuxt-sdk-latest.md
• packages/cli-core/src/lib/framework.ts

📝 Walkthrough

Walkthrough

This change removes a pinned snapshot version constraint for Nuxt SDK installation. The changeset file documents that clerk init --starter will now install @clerk/nuxt@latest instead of the previously pinned @clerk/nuxt@2.2.0-snapshot.v20260413174426. The corresponding code change in framework.ts removes the sdkInstall override from the Nuxt framework configuration in FRAMEWORK_MAP, allowing it to rely on the standard SDK package specifier.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing the pinned Nuxt SDK version override now that keyless support is stable.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description clearly explains the rationale for removing the pinned Nuxt SDK version, provides context about when keyless support shipped in stable, and outlines the testing performed.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 55 minutes and 40 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

.changeset/nuxt-sdk-latest.md (1)

5-5: 💤 Low value

Minor wording/narrative consistency check for changelog accuracy.

Line [5] makes several version-specific claims (“keyless support shipped in stable @clerk/nuxt@2.2.0” and that the snapshot pin is “no longer needed”). This is fine, but since it’s user-facing release/changelog text, please ensure it matches the actual @clerk/nuxt release notes/tag history you used when making the change.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.changeset/nuxt-sdk-latest.md at line 5, Changelog wording references
specific versions and claims ("keyless support shipped in stable
`@clerk/nuxt`@2.2.0" and removal of the snapshot pin) that must match the actual
`@clerk/nuxt` release history; verify the `@clerk/nuxt` release notes/tags for
keyless support and the meaning of the snapshot tag, then update the sentence
that mentions `clerk init --starter`, `@clerk/nuxt@latest`, `@clerk/nuxt@2.2.0`,
and the snapshot tag (`@2.2.0-snapshot.v20260413174426`) to accurately reflect
whether keyless support landed in 2.2.0 and whether the snapshot pin is truly
unnecessary (or rephrase to a non-absolute claim like "the snapshot pin is no
longer required for most users" if uncertain).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.changeset/nuxt-sdk-latest.md:
- Line 5: Changelog wording references specific versions and claims ("keyless
support shipped in stable `@clerk/nuxt`@2.2.0" and removal of the snapshot pin)
that must match the actual `@clerk/nuxt` release history; verify the `@clerk/nuxt`
release notes/tags for keyless support and the meaning of the snapshot tag, then
update the sentence that mentions `clerk init --starter`, `@clerk/nuxt@latest`,
`@clerk/nuxt@2.2.0`, and the snapshot tag (`@2.2.0-snapshot.v20260413174426`) to
accurately reflect whether keyless support landed in 2.2.0 and whether the
snapshot pin is truly unnecessary (or rephrase to a non-absolute claim like "the
snapshot pin is no longer required for most users" if uncertain).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8a62d179-1c20-4e23-be48-2473a432e3c7

📥 Commits

Reviewing files that changed from the base of the PR and between 2eabbf5 and 2ce88f7.

📒 Files selected for processing (2)

• .changeset/nuxt-sdk-latest.md
• packages/cli-core/src/lib/framework.ts

💤 Files with no reviewable changes (1)

• packages/cli-core/src/lib/framework.ts

[rafa-thayto]

!snapshot

[github-actions]

Snapshot published

npm install -g clerk@1.1.1-snapshot.e0464af

Package	Version
clerk	1.1.1-snapshot.e0464af

Published from e0464af