Repository navigation
MV-21235 - Creating minor SDK release for upcoming TFV breaking changes - #314
Open
adamrbaldwin-bw wants to merge 1 commit into
Open
adamrbaldwin-bw wants to merge 1 commit into
adamrbaldwin-bw wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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.
Summary
Regenerates this SDK from the spec changes in Bandwidth/api-specs#2566 (
MV-21235) so a new minor version can be released ahead of upcoming Toll-Free Verification (TFV) changes. This lets customers adopt the new request shape before the API enforces it.Upcoming TFV changes
businessEntityType. When it is anything other thanSOLE_PROPRIETOR,businessRegistrationNumber,businessRegistrationTypeandbusinessRegistrationIssuingCountryare also required.SOLE_PROPRIETORsubmissions must omit all three. Violations return400 Bad Request.409 Conflict(new409response documented on the submit and update endpoints; delete will cancel an in-progress verification).Why release now
The API already accepts
businessEntityTypeand the registration fields today, so the updated SDK is compatible with the current API. Releasing before the changes take effect lets customers upgrade and start sending the new fields on their own schedule.SDK changes
businessEntityTypeis now required on the TFV request models. This is a compile/validation-time change for callers who omit it.409handling docs.main.Notes for review
bandwidth.ymlcomes from the unmerged api-specs PR, which is planned to merge Monday, Oct 19, before the next weeklyupdate-sdksrun. The weekly run should then produce no diff for this SDK.combine-specs.shandgenerate.sh; unrelated example-value churn was discarded.🤖 Generated with Claude Code