Pavel Batanov either is fine, since it needs to operate correctly with both 1.16.1 and 1.17.0. I'm currently running the pre-release with git client plugin 1.17.0 in my home instance in in my production Jenkins at work. If you're running with 1.16.1, that increases our chances of detecting problems related to version interactions.
Since the bug was only exposed with git client plugin 1.17.0, you should not see the problem in your configuration. The goal of your testing is to confirm that other things are not broken unexpectedly in the git plugin 2.3.6 release.