Adrien Piquerez
Adrien Piquerez
I closed this issue because I believe that #1521 is enough to resolve it. > At the moment, the Scaladex is doing a GraphQL query per user-organisation. I don't know...
Just to be sure, have you tried unlogging and logging again? If yes and it is not working, it is probably not going to work better in half an hour.
@rtyley I need your help to fix this. Using the Graph API I can see that you have admin rights in `rtyley/scanamo` but I don't see anything about `scanamo/scanamo`. It...
> On the other hand, a concrete problem solved now is better than a theoretical problem solved with a theoretical change where we don't know how it will look. So...
[Bug] Scaladex not finding the latest artficat after migrating project to `Maven Central Repository`
Thank you all for reporting these missing artifacts. I am starting the investigation.
[Bug] Scaladex not finding the latest artficat after migrating project to `Maven Central Repository`
I found the root cause of version 1.2.2 missing for this neotypes project. The problem is the scm info in the 1.2.2 POM files point to [BalmungSan/neotypes](https://github.com/BalmungSan/neotypes) which is a...
[Bug] Scaladex not finding the latest artficat after migrating project to `Maven Central Repository`
And the reason why Scaladex does not compute the correct latest version is because there are artifacts with same group id an artifact id in the 2 different projects. This...
[Bug] Scaladex not finding the latest artficat after migrating project to `Maven Central Repository`
I pushed the fix, but it is not yet deployed.
[Bug] Scaladex not finding the latest artficat after migrating project to `Maven Central Repository`
> Oh, so maybe I should rather fix that? I have always run the release process manually from my fork, but it has always pointed to the right repo, right?...
[Bug] Scaladex not finding the latest artficat after migrating project to `Maven Central Repository`
The fix is deployed. See https://index.scala-lang.org/neotypes/neotypes/artifacts