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

Pre-release floating version doesn't resolve to the latest package. #7880

Closed
DevKumar4Git opened this Issue Mar 14, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@DevKumar4Git
Copy link

DevKumar4Git commented Mar 14, 2019

I have this in my proj file.

<ItemGroup>
    <PackageReference Include="PackageName" Version="0.1-*"/>
</ItemGroup>

On my feed, these are the pre-release packages with versioning implemented as Major.Minor.Patch. Patch gets incremented on a daily build.
0.1.35-alpha-313f0dda
0.1.38-alpha-ae402cd9
0.1.41-alpha-630080c4
0.1.42-alpha-f5e4e8e7
0.1.43-alpha-1942086d

The floating version 0.1-* doesn’t pick up the latest package, rather it gets the lowest one (0.1.35-alpha*).

Is there a workaround to this?

@rrelyea

This comment has been minimized.

Copy link
Contributor

rrelyea commented Mar 14, 2019

We don't have support for "x.y.-" yet, but are planning on something like that in the future.
So, don't think you have the ability to float prerelease, given your versioning strategy.

If you could keep the third set of digits to be the same, then you could float the prerelease part of version:
"0.1.0-*"

@rrelyea

This comment has been minimized.

Copy link
Contributor

rrelyea commented Mar 14, 2019

Note...this request is covered in: #912

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.