Yichao YangandGitHub 050a841f99 Separate version history Add and Switch (#6500) ...

## What changed?
<!-- Describe what has changed in this PR -->
- Separate util func for version history Add and Switch

## Why?
<!-- Tell your future self why have you made these changes -->
- In state-based replication world, current history version history can
have a smaller version than other history branches. This auto switch
logic will break that and needs to be separated.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- Existing unit test

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

2024-09-09 21:28:59 +00:00

..

api_test.go

Separate version history Add and Switch (#6500)

2024-09-09 21:28:59 +00:00

api.go

Import alignment (#6426)

2024-08-23 14:48:10 -06:00