Added the description for the version field #1609
Merged
Conversation
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
pja-ant
previously approved these changes
Oct 6, 2025
jonathanhefner
previously approved these changes
Oct 7, 2025
auto-merge was automatically disabled
October 25, 2025 07:29
Head branch was pushed to by a user without write access
Contributor
Author
|
@pja-ant @jonathanhefner thank you for approving. There was a merge conflict on this PR, I resolved it but now it requires your blessing once again. |
jonathanhefner
previously approved these changes
Oct 27, 2025
Contributor
|
@a-akimov - mind resolving the conflict once more? |
Contributor
Author
localden
approved these changes
Jan 26, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Motivation and Context
The version field is returned in many places, so it would be good to have a description. I propose to start with a basic one, since we don't mandate whether it should be semver, or date-based or any other types of versioning. (as far as I know)
How Has This Been Tested?
Locally.
Breaking Changes
No.
Types of changes
Checklist
Additional context
Was originally in this PR