You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2022. It is now read-only.
Your developer guide page points to the semversion 2.0.0 webpage, but your issue is for a 1.0.0 part of the spec. 2.0.0 has removed this suggestion and now has this in the FAQ: https://semver.org/#is-v123-a-semantic-version
If you are intending to use semver 1.0.0, then the link might need to be updated. Otherwise, it would be better to state this is for consistency with other parts of the cnab project.
@thaney071 Correct, as Glyn said we would like to be consistent with the other cnabio projects which use the v prefix for our git tags.
We do follow semver 2 for the CNAB spec for bundle version by the way, the bundle.json version field doesn't use a v prefix. This issue is only applicable to the git tag for this repo.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is for consistency with cnab-go.
Also https://semver.org/spec/v1.0.0.html#tagging-specification-semvertag favours this:
The text was updated successfully, but these errors were encountered: