mirror of
https://github.com/semver/semver.git
synced 2026-07-11 04:52:47 -05:00
[GH-ISSUE #876] semver version in yaml format #5682
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Sep 21, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/876
Hi everyone.
I would like to know if you all have ever thought about creating a semver file in Yaml. Would it be possible to have a semver.yaml file?
semver.yaml
@JohnTitor commented on GitHub (Sep 21, 2022):
The current comment doesn't describe what that YAML file does, could you clarify? What do you want for the semver specification?
@ghost commented on GitHub (Sep 21, 2022):
Hi JohnTitor. So...
YAML is a human-friendly data serialization.
I would like to know if you all have ever thought about creating a semver file in Yaml... because... in my opinion it would make sense to create a semver specification in yaml for better semantics. YAML is a human-friendly data serialization and semver is "semantic versioning specification". Therefore, it would make sense to have a formatted file... semver in yaml format.
@JohnTitor commented on GitHub (Sep 21, 2022):
Hmm, I don't think specification is a data type.
So you want to express the specification with YAML? But your YAML file just lists version numbers and some even don't follow semver (e.g.
1.0.1a).AFAIK no.
@ljharb commented on GitHub (Sep 21, 2022):
What is a “semver file”?
@ghost commented on GitHub (Sep 21, 2022):
Hi JohnTitor.
I said something wrong, so please sorry me.
Exactly... yeah... as:
semver.yaml
@ghost commented on GitHub (Sep 21, 2022):
Hi ljharb.
A semver file is a semantic expression about software versioning in yaml format(which is also semantic).
@ljharb commented on GitHub (Sep 21, 2022):
@codehangen that doesn't clear it up. Semver means that the version triple - x.y.z (possibly with a prerelease or build identifier) - encapsulates the entirety of the semantics, which means that the format of the file containing it is utterly irrelevant.
@ghost commented on GitHub (Sep 21, 2022):
Hi ljharb, JohnTitor. thank you all for feedback, so please... could you all close this issue?