feat: drop create sms endpoint #39
Merged
Conversation
This file contains 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
Nikpolik
force-pushed
the
nikpolik/drop-create_sms-endpoint
branch
from
d069ba6 to
3d5c311
Compare
This feature is beeing dropped from our 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.
Nikpolik
force-pushed
the
nikpolik/drop-create_sms-endpoint
branch
from
3d5c311 to
d1d7820
Compare
gkats
approved these changes
Nov 20, 2023
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.
Remove
createSmsfunctions fromclerk-sdk-ruby.The equivalent
/sms_messageswill also removed in the future, since this feature will no longer be available for new instances.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 this resource.