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
cs update
not finding new versions without --mode force
#2603
Comments
If this is the same issue as I described in scala-steward-org/scala-steward#2797 (comment), downgrading cs to 2.1.0-RC1 would fix it. |
Yea the tricky part is that now all the cache is refreshed I don't have the same problem. So it's a bit hard to reproduce. |
See issue coursier/coursier#2603 and PR coursier/coursier#2591 Pull request: #2163
Alright I was just able to confirm this. I released some new artifacts today and was unable to fetch them or see them:
Just returned nothing. I then did the following:
And everything then worked. |
I've noticed a couple different people on Discord having issues with having old version installed by
scala-cli
. For example I saw this issue with Bloop and with Metals. I runcs update
in a morning script that I have every day so I sort of always expect my stuff to be up to date, but today I realized myscala-cli
version was out of date. Even with a fresh install I wasn't getting the new one and wouldn't unless I used--mode force
. For example here are the steps I took to illustrate this:Output of cs version
I recently came across this issue in Scala Steward scala-steward-org/scala-steward#2797 and I wonder if these could be related?
The text was updated successfully, but these errors were encountered: