Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suggestion: use Semantic Versioning #17

Open
sinkcup opened this issue Dec 17, 2021 · 1 comment
Open

suggestion: use Semantic Versioning #17

sinkcup opened this issue Dec 17, 2021 · 1 comment

Comments

@sinkcup
Copy link

sinkcup commented Dec 17, 2021

most of composer packages use Semantic Versioning, such as 1.2.3, not 1.2.3.4

image

docs: https://semver.org/
https://getcomposer.org/doc/articles/versions.md

if need build number, use 1.2.3+80, not 1.2.3.80

Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata MUST be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85, 1.0.0+21AF26D3—-117B344092BD.

@danog
Copy link
Contributor

danog commented Dec 17, 2021

+, good idea, will implement.
Thanks for the tip!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants