-
Notifications
You must be signed in to change notification settings - Fork 254
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
feat(backend,clerk-sdk-node): Drop create sms endpoint #2165
Conversation
🦋 Changeset detectedLatest commit: c76832e 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 |
a890c6d
to
ca21b16
Compare
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.
@Nikpolik This looks good to me :)
If we haven't done that already, we need to add deprecation warnings to the methods in the release/v4
branch as well, letting our users know that these endpoints will be removed.
ca21b16
to
1c4cfa1
Compare
@nikosdouvlis I added dba09d9 and will cherry pick this commit to release/v4 after merging! |
65d07ee
to
6a6b1cc
Compare
|
||
Deprecate `createSMSMessage` and `SMSMessageApi` from `clerkClient`. | ||
|
||
The equivalent `/sms_messages` Backend API endpoint will also be dropped in the future, since this feature will no longer be available for new instances. |
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.
The equivalent `/sms_messages` Backend API endpoint will also be dropped in the future, since this feature will no longer be available for new instances. | |
The `/sms_messages` Backend API endpoint will also be dropped in the future since this feature will no longer be available for new Clerk instances. |
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.
@SokratisVidros I had enabled auto merge from yesterday and did not get a chance to update the copyright 😓
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.
Its updated in #2184 which is for v4 release
This feature is beeing dropped from the Backend API. For a brief period it will still be available for instances that have used it in the past 7 days (13-11-2023 to 20-11-2023). New instances will get a 403 forbidden response if they try to access it.
6a6b1cc
to
c76832e
Compare
* feat(backend): Deprecate createSMSMessage * feat(backend,clerk-sdk-node): Drop create sms endpoint This feature is beeing dropped from the Backend API. For a brief period it will still be available for instances that have used it in the past 7 days (13-11-2023 to 20-11-2023). New instances will get a 403 forbidden response if they try to access it.
Remove
createSms
functions from@clerk/backend
and@clerk/sdk-node
.The equivalent
/sms_messages
Backend API endpoint will also be dropped in the future, since this feature will no longer be available for new instances.For a brief period it will still be accessible for instances that have used it in the past 7
days (13-11-2023 to 20-11-2023).
New instances will get a 403 forbidden response if they try to access it.