How to toggle Scaladex into including a new version of your repo?

Question
1

I read that there still a problem with Scaladex picking up latest versions of repos automatically. Is there a way to manually do this? My repo on maven is three months and two versions behind the repo on Scaladex.

2

From what I know there isn’t an issue with ScalaDex picking a new version/new library.

There is an issue, that Sonatype nuked their old repo, which had a hook calling ScalaDex with updates, so there are no updates received by ScalaDex, while at the same time there is an explicit ban for scrapping the content naively.

So the team is working on a completely re-done approach to be able to get some updates, somehow, without breaking the ToC, there are some ideas how (from what I understood there is an API to pull diffs, and this way see what was published since the last date), but they are not yet implemented, and until they do there won’t be any updates on ScalaDex at all.

1 Like
3

That’s too bad. Maybe it is an idea to add a button in the account environment so that members can manually trigger the update call for their repo only? That’s no scrap, and hopefully easy to implement.

4

From what I understand there is simply a rate-limiter - if enough people will press “refresh” it will block out the fetcher anyway. Diff fetcher would make it slightly leaner, and the issue isn’t even in complexity I think, but more in that there is virtually 1/2 guys maintaining it spread across: Scaladex, Metals, Scala Meta, etc.

5

We are in conversation with Sonatype about this, so hopefully we will have some updates later this month.

1 Like
6

Somebody pulled a string … my repo is up :smiley:
Thank you!

7

I do try to run some updates manually, but that’s only a bandaid unfortunately.

8

Hmm. Would there be any value to having a “please update” button on a repo page? It’s kind of a crude workaround, but providing a way for library creators or users to say “I think you’re behind; please update” would at least outsource that manual work for you.

1 Like
9

I still hope we can fix this without a workaround after talking to Sonatype. If we are unable to do that, I will probably add some new option.

1 Like
10

That’d be pretty easy to automate in a release script.