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

Install without full name for release candidate no longer works #133

Closed
GGG-KILLER opened this issue Sep 25, 2020 · 3 comments
Closed

Install without full name for release candidate no longer works #133

GGG-KILLER opened this issue Sep 25, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@GGG-KILLER
Copy link
Contributor

Description

Using 5.0.100-rc.1 as the version instead of 5.0.100-rc.1.20452.10 no longer works.

I wasn't able to pinpoint the issue as v1.6.0, v1.7.0 and v1.7.1 all fail to install it. It was working a few days ago but now it no longer works.

I'm not sure if the issue is in the setup scripts or somewhere else.

@ZEisinger ZEisinger added the bug Something isn't working label Oct 8, 2020
@vsafonkin
Copy link

Hi @GGG-KILLER , looks like it stopped working for installer' scripts as the value of version is passed to them. Maybe it makes sense to open issue in dotnet/install-scripts repo.

@GGG-KILLER
Copy link
Contributor Author

GGG-KILLER commented Feb 10, 2021

Hi @GGG-KILLER , looks like it stopped working for installer' scripts as the value of version is passed to them. Maybe it makes sense to open issue in dotnet/install-scripts repo.

Right, but the logic that handles 5.0.x should also be able to handle this, shouldn't it?

@vsafonkin
Copy link

Yes, but now the task does not support finding pre-release version. I believe your PR will be merged soon and it will be work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants