Bump version for veriffSessionId support#53
Merged
Conversation
The validate-challenge response now includes veriffSessionId when the challenge was a Veriff session. The SDK already passes new response fields through verbatim, so no code changes are needed. Bumps version to 5.5.0.
LittleJono
approved these changes
Apr 24, 2026
The API now validates phoneNumber against E.164 format. +6427000000 was rejected as invalid, causing enroll_verified_authenticator to fail silently (HTTP 400 returned as a response body, not raised as an error) and downstream assertions about enrollment state to fail. Replaces with +6427123456, which is valid E.164 and already used elsewhere in the same file.
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
2 participants
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
veriffSessionIdwhen the challenge was a Veriff session.5.5.0.