-
Notifications
You must be signed in to change notification settings - Fork 722
[release] use semantic versioning format #692
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
Conversation
You can see the
To check that it works on release, use:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
To follow up on my concern yesterday, the spec dispels it:
[...] A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version
bors r+
692: [release] use semantic versioning format r=ricab a=Saviq Adhere to https://semver.org/, using the latest tag, number of commits since latest annotated tag and commit abbreviation as version, pre-release identifier and build metadata, respectively. Co-authored-by: Michał Sawicz <michal@sawicz.net>
Oops, another review pending... bors r- |
Canceled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
bors r+
692: [release] use semantic versioning format r=gerboland a=Saviq Adhere to https://semver.org/, using the latest tag, number of commits since latest annotated tag and commit abbreviation as version, pre-release identifier and build metadata, respectively. Co-authored-by: Michał Sawicz <michal@sawicz.net>
bors r- |
Canceled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep
bors r+
692: [release] use semantic versioning format r=gerboland a=Saviq Adhere to https://semver.org/, using the latest tag, number of commits since latest annotated tag and commit abbreviation as version, pre-release identifier and build metadata, respectively. Co-authored-by: Michał Sawicz <michal@sawicz.net>
For posterity:
|
Build failed |
4122d7f
to
cfba1fe
Compare
Adhere to https://semver.org/, using the latest tag, number of commits since latest annotated tag and commit abbreviation as version, pre-release identifier and build metadata, respectively.
Apparently that messes with the build config.
bors r=greyback,ricab |
692: [release] use semantic versioning format r=greyback,ricab a=Saviq Adhere to https://semver.org/, using the latest tag, number of commits since latest annotated tag and commit abbreviation as version, pre-release identifier and build metadata, respectively. Co-authored-by: Michał Sawicz <michal@sawicz.net>
Codecov Report
@@ Coverage Diff @@
## master #692 +/- ##
=======================================
Coverage 66.59% 66.59%
=======================================
Files 168 168
Lines 5943 5943
=======================================
Hits 3958 3958
Misses 1985 1985 Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #692 +/- ##
=======================================
Coverage 66.59% 66.59%
=======================================
Files 168 168
Lines 5943 5943
=======================================
Hits 3958 3958
Misses 1985 1985 Continue to review full report at Codecov.
|
Build succeeded |
Adhere to https://semver.org/, using the latest tag, number of commits since
latest annotated tag and commit abbreviation as version, pre-release
identifier and build metadata, respectively.