-
Notifications
You must be signed in to change notification settings - Fork 403
feat(backend): Deprecate createSMSMessage #2184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: c3e24e2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔧 You will also need to use deprecated() method from @clerk/shared/deprecated inside the createSMSMessage()
Is there a replacement for this API or is it completed dropped?
It's completely dropped. |
f5fd5e3 to
a8e1592
Compare
|
@dimkl Thanks, I added the |
a8e1592 to
145aba4
Compare
145aba4 to
c3e24e2
Compare
Description
The deprecation commit of #2165 for release in v4
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change
Packages affected
@clerk/backend@clerk/chrome-extension@clerk/clerk-js@clerk/clerk-expo@clerk/fastifygatsby-plugin-clerk@clerk/localizations@clerk/nextjs@clerk/clerk-react@clerk/remix@clerk/clerk-sdk-node@clerk/shared@clerk/themes@clerk/typesbuild/tooling/chore