Comply with semantic versioning pre-release format #6509
Merged
Conversation
This file contains hidden or 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
3 tasks
jayschwa
force-pushed
the
semver-prerelease
branch
from
015e991 to
3d323b5
Compare
jayschwa
force-pushed
the
semver-prerelease
branch
from
3d323b5 to
bcf338d
Compare
|
I wanted to get this (and #6566) in by 0.7.0 but ran out of time to do it early enough to do due diligence to fix possible breakage from this change. So I'm sorry to do this but I don't think we're going to have this feature in 0.7.0. This will be another "unstable" release, with no 0.7.1 planned. But after 0.8.0 it's planned to have bug fix releases after that, so that would be the time to have some semblance of stability. |
Example version: 0.8.0-dev.460+g81b343a16 From a semantic versioning perspective, development builds will now be considered distinct from a tagged release. The number of commits added since the last tag is included in the pre-release component. Updates ziglang#6466
jayschwa
force-pushed
the
semver-prerelease
branch
from
bcf338d to
4b8313e
Compare
|
Rebased and tweaked for 0.8.0 development. |
|
Thanks @jayschwa! |
|
Thanks for merging. While starting on the final step of proposal #6466, I noticed that I may have missed some parallel Git parsing and version construction logic in the repo's top level |
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Dec 30, 2020
This matches the behavior of CMake builds. These changes should have gone in with PR ziglang#6509, but were missed.
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Dec 30, 2020
This matches the behavior of CMake builds. These changes should have gone in with PR ziglang#6509, but were missed.
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Dec 30, 2020
This matches the behavior of CMake builds. These changes should have been in PR ziglang#6509, but were missed.
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Dec 30, 2020
This matches the behavior of CMake builds. These changes should have been in PR ziglang#6509, but were missed.
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Dec 30, 2020
This matches the behavior of CMake builds. These changes should have been in PR ziglang#6509, but were missed.
Closed
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Jan 1, 2021
`git describe` is used for version string creation, but it had to be reverted in commit 69da6ba because it was broken in CI builds. Azure Pipelines and Drone perform shallow clones by default. This change reconfigures them to do normal clones and fetch tags. This adds an extra 10-20 seconds, which is negligible compared to overall build and test time. Related: ziglang#6466, ziglang#6509, ziglang#7601
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Jan 1, 2021
git describe is used for version string creation, but it had to be reverted in commit 69da6ba because it was broken in CI builds. Azure Pipelines and Drone perform shallow clones by default. This change reconfigures them to fetch history and tags. It adds tens of seconds, which is negligible compared to overall build and test time. Related: ziglang#6466, ziglang#6509, ziglang#7601
jayschwa
added a commit
to jayschwa/zig
that referenced
this pull request
Jan 2, 2021
git describe is used for version string creation, but it had to be reverted in commit 69da6ba because it was broken in CI builds. Azure Pipelines and Drone perform shallow clones by default. This change reconfigures them to fetch history and tags. It adds tens of seconds, which is negligible compared to overall build and test time. Related: ziglang#6466, ziglang#6509, ziglang#7601
andrewrk
pushed a commit
that referenced
this pull request
Jan 2, 2021
git describe is used for version string creation, but it had to be reverted in commit 69da6ba because it was broken in CI builds. Azure Pipelines and Drone perform shallow clones by default. This change reconfigures them to fetch history and tags. It adds tens of seconds, which is negligible compared to overall build and test time. Related: #6466, #6509, #7601
aarvay
pushed a commit
to aarvay/zig
that referenced
this pull request
Jan 4, 2021
This matches the behavior of CMake builds. These changes should have been in PR ziglang#6509, but were missed.
aarvay
pushed a commit
to aarvay/zig
that referenced
this pull request
Jan 4, 2021
git describe is used for version string creation, but it had to be reverted in commit 69da6ba because it was broken in CI builds. Azure Pipelines and Drone perform shallow clones by default. This change reconfigures them to fetch history and tags. It adds tens of seconds, which is negligible compared to overall build and test time. Related: ziglang#6466, ziglang#6509, ziglang#7601
dgbuckley
pushed a commit
to dgbuckley/zig
that referenced
this pull request
Mar 9, 2021
This matches the behavior of CMake builds. These changes should have been in PR ziglang#6509, but were missed.
dgbuckley
pushed a commit
to dgbuckley/zig
that referenced
this pull request
Mar 9, 2021
git describe is used for version string creation, but it had to be reverted in commit 69da6ba because it was broken in CI builds. Azure Pipelines and Drone perform shallow clones by default. This change reconfigures them to fetch history and tags. It adds tens of seconds, which is negligible compared to overall build and test time. Related: ziglang#6466, ziglang#6509, ziglang#7601
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.
Example version: 0.8.0-dev.460+g81b343a16
From a semantic versioning perspective, development builds will now be
considered distinct from a tagged release. The number of commits added
since the last tag is included in the pre-release component.
Updates #6466