Repository navigation
Version main's previews after the latest release tag - #1315
Merged
Merged
Conversation
3.0.0 is released, and 3.0.0-preview builds would sort below it.
Previews were versioned from VersionPrefix, which had to be bumped by hand after each release or they sorted below it. They now take the highest release tag: 3.0.1-preview.<run> after 3.0.0, or 3.1.0-beta.1.preview.<run> after 3.1.0-beta.1.
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
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.
Builds of main publish preview packages to feedz.io, versioned
<VersionPrefix>-preview.<run number>. Since 3.0.0 was released, those3.0.0-preview.*builds sort below it, and avoiding that meant bumpingVersionPrefixby hand after every release.The Build workflow now derives the preview version from the release tags (read with
git ls-remote, so it works on the shallow checkout and sees tags from every branch):v3.0.0(today)3.0.1-preview.<run>v3.1.0-beta.23.1.0-beta.2.preview.<run>v3.0.5from a release branch3.0.6-preview.<run>3.0.0-preview.*packages already on the feed..github/scripts/preview-version.pydoes the SemVer ordering (sort -Vplacesv3.0.0belowv3.0.0-beta.9).VersionPrefixstays as is: it no longer affects published packages. The README's preview section describes the scheme.Tested the script against the live tags (
3.0.1-preview.916) and against betas, release candidates, out-of-order and non-version tags.