refactor(express): split login endpoint into V1 and V2#8586
Open
rishikeshdadam136 wants to merge 1 commit intomasterfrom
Open
refactor(express): split login endpoint into V1 and V2#8586rishikeshdadam136 wants to merge 1 commit intomasterfrom
rishikeshdadam136 wants to merge 1 commit intomasterfrom
Conversation
cddd275 to
102721b
Compare
Contributor
Author
|
Tested in local for both v1 and v2 |
102721b to
e6c756b
Compare
e6c756b to
9e915f2
Compare
6105329 to
49b1ad3
Compare
49b1ad3 to
fc27898
Compare
fc27898 to
5837659
Compare
mrdanish26
reviewed
Apr 24, 2026
Contributor
mrdanish26
left a comment
There was a problem hiding this comment.
CI failure, flushing the queue
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.
Ticket: WCI-186
Context - https://bitgo.slack.com/archives/C057BHBRG4B/p1764020095794829?thread_ts=1764018507.602879&cid=C057BHBRG4B
The API behavior is not changing. We are splitting the combined v[12] route into two separate V1 and V2 routes, so both will continue to work and clients will not be affected.