Repository navigation
fix(deps): update dependency com.vonage:server-sdk to v9.14.0 (main) - autoclosed - #127
Closed
mend-for-github-com[bot] wants to merge 1 commit into
Closed
mend-for-github-com[bot] wants to merge 1 commit into
mend-for-github-com[bot] wants to merge 1 commit into
Conversation
mend-for-github-com
Bot
force-pushed
the
whitesource-remediate/main-com.vonage-server-sdk-9.x
branch
from
October 14, 2026 20:08
c1f7f4f to
8a96ba5
Compare
mend-for-github-com
Bot
force-pushed
the
whitesource-remediate/main-com.vonage-server-sdk-9.x
branch
from
October 17, 2026 00:46
8a96ba5 to
aa43f72
Compare
mend-for-github-com
Bot
deleted the
whitesource-remediate/main-com.vonage-server-sdk-9.x
branch
October 18, 2026 03:49
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.
This PR contains the following updates:
9.3.1→9.14.0By merging this PR, the issue #123 will be automatically resolved and closed:
Release Notes
Vonage/vonage-java-sdk (com.vonage:server-sdk)
v9.14.0RequestSigning.verifyRequestSignature(InputStream, String, Map, String, HashType)overload, so callers can verify signed callbacks (e.g. SMS) using a non-MD5 algorithm such asHMAC_SHA256. Previously the only publicly accessible overload was hardcoded toHashType.MD5and the algorithm-aware overload was package-private. Existing overloads are unchanged and still default to MD5v9.13.1trusted_recipientbeing serialized nested inside thesmssettings object instead of at the top level of the message body, soSmsTextRequest.builder().trustedRecipient(...)now matches the Messages API contract (MMS and RCS were already correct). Removed the incorrectly placedtrusted_recipientaccessor fromOutboundSettings; useSmsTextRequest.getTrustedRecipient()insteadv9.13.0tofield, in addition to a phone number. The recipient is accepted as-is (phone numbers are normalised) and not validated against a client-side format, so values accepted by the API are never rejected by the SDKWhatsappUsermodel (user_id,parent_user_id,wa_id)InboundMessage: addedwhatsapp.senderviagetWhatsappSender()MessageStatus: addedwhatsapp.recipientviagetWhatsappRecipient()and WhatsAppprofileviagetWhatsappProfile()Profile: addedgetUsername()v9.12.0v9.11.0client-ref) maximum length from 40 to 100 characters, matching the Messages APIv9.10.2Connection reseterrors when reusing long-livedVonageClientinstancesv9.10.1v9.10.0getRawRequest()andgetRawResponse()methods toVonageApiResponseExceptionfor debugging API errors2592000secondsv9.9.0template_idparameterv9.8.0trusted_recipientto SMS, MMS, and RCSpool_idsupportsandboxparametershakensigning on callssip_codeon incoming event webhooksv9.7.0v9.6.0v9.5.0trusted-numberto SMSv9.4.2TextToSpeechLanguageenumv9.4.1v9.4.0bidirectionalflag for websockets to support the new Bi-Directional Audio Connector