Standardize version file format #1553
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
4 tasks
YisDav
force-pushed
the
change/1548-version-file-standardization
branch
3 times, most recently
from
52cae2d to
8d7463a
Compare
Enaraque
previously approved these changes
Feb 17, 2025
YisDav
force-pushed
the
change/1548-version-file-standardization
branch
from
8d7463a to
da54387
Compare
YisDav
force-pushed
the
change/1548-version-file-standardization
branch
from
da54387 to
856f9b3
Compare
c-bordon
approved these changes
Feb 17, 2025
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.
Description
This pull request introduces an enhancement to the version file format. The file has been renamed from
VERSIONtoVERSION.json, and its content structure has been updated to comply with JSON standards.Related Issue