Skip to content

dev & test: bump deps #389

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

Merged
merged 2 commits into from
May 27, 2025
Merged

dev & test: bump deps #389

merged 2 commits into from
May 27, 2025

Conversation

lread
Copy link
Collaborator

@lread lread commented May 27, 2025

No description provided.

@lread
Copy link
Collaborator Author

lread commented May 27, 2025

Ah. refactor-nrepl lib test is failing because it depends on search.maven.org, which status shows as currently down:

image

Lotsa downtime on search.maven.org of late.

@lread
Copy link
Collaborator Author

lread commented May 27, 2025

Fired off an email to sonatype to offer my help (if that makes any sense) in restoring stability to search.maven.org.

@lread
Copy link
Collaborator Author

lread commented May 27, 2025

Looks like search.maven.org is back up again!

@lread lread merged commit cda543f into main May 27, 2025
85 checks passed
@lread
Copy link
Collaborator Author

lread commented May 27, 2025

Sonatype did get back to me. They don't seem to need my help at this time.

They wrote:

Unfortunately we have divested resources away from search.maven.org in favour of https://central.sonatype.com/ & are in the process of retiring that service from the web.
You can find more information on this here. Sorry for any inconvenience this may have caused.

I clarified usage in a reply:

I should have been clearer that my usage of search.maven.org is for the REST API as documented here: https://central.sonatype.org/search/rest-api-guide/

So, I think you are saying this current REST API will likely be shaky until a new one is created, but the new REST API is not available yet.
Is that right?

And they confirmed:

Yes, that is correct. We plan on making a more official statement once we have determined the next course of action for our users still using the old api. We apologize for any disruptions that may have been caused by this in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant