{{ message }}
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>
Contributor
|
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 packagesNot 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 |
manovotny
marked this pull request as ready for review
October 20, 2026 14:42
This branch had an error being deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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