Print detailed client version in the log #568
Merged
Conversation
This file contains 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
SadPencil
force-pushed
the
feat-detailed-client-version
branch
from
8f70117
to
54da550
Compare
|
Nightly build for this pull request:
|
Metadorius
approved these changes
Nov 3, 2024
SadPencil
force-pushed
the
feat-detailed-client-version
branch
from
54da550
to
ecda849
Compare
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 prints detailed client version ("ProductVersion") in the log, for example,
2.12.0-feat-detailed-client-version.1+9.Branch.feat-detailed-client-version.Sha.54da550909971152332380ca79fe1b732501ec3a. Containing the git commit should be extremely helpful to minimize the mess and determine the client version if a user uses a non-release build.