Repository navigation
Conversation
Same fix as #9863 for two more packages main no longer publishes. Their `latest` versions are deprecated, but every Core 2 release since adds an undeprecated version that a bare `npm install` resolves to with no warning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
🦋 Changeset detectedLatest commit: e8ee950 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
This branch had an error being deployed
1 participant
Description
Same fix as #9863, for two more packages main no longer publishes.
@clerk/elementswas dropped in Core 3 (#7271), and@clerk/agent-toolkitwas removed in #8330. Both have a deprecatedlatest, but every Core 2 release since has published newer undeprecated versions, so a barenpm installresolves to@clerk/elements@0.24.21or@clerk/agent-toolkit@0.2.36with no warning.This sets
deprecatedin bothpackage.jsonfiles, and the changeset patch-releases them so the newest versions carry it right away. Nothing else cascades.@clerk/elementsreuses the message itslatestalready shows.@clerk/agent-toolkitgets "This package is no longer supported." instead of the message on itslatest, which is npm's generic "Contact Support at npmjs.com" text.The versions already published (0.24.14–0.24.21 and 0.2.31–0.2.36) still need a one-off
npm deprecateafter this merges.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
🤖 Generated with Claude Code