datasource/sbt-plugin doesn't support registries that doesn't allow dir listing #33637
pnordh
started this conversation in
Suggest an Idea
Replies: 2 comments 1 reply
-
cc @sschoebinger @zharinov @fernandomora as you worked on the previous implementations (linked above) |
Beta Was this translation helpful? Give feedback.
1 reply
-
Here's example Renovate logs from when it fails to look up an sbt plugin from Google Artifact Registry: DEBUG: GET https://europe-maven.pkg.dev/myproject/myregistry/com.myorg/ = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=404 retryCount=0, duration=119)
DEBUG: GET https://europe-maven.pkg.dev/myproject/myregistry/com/myorg/myplugin/ = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=404 retryCount=0, duration=380)
DEBUG: GET https://europe-maven.pkg.dev/myproject/myregistry/com/myorg/ = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=404 retryCount=0, duration=118)
DEBUG: No versions found for com.myorg:myplugin in 2 repositories
DEBUG: Failed to look up sbt-plugin package com.myorg:myplugin
{
"dependency": "com.myorg:myplugin"
"packageFile": "project/plugins.sbt"
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tell us more.
Same issue reported for the
sbt-package
datasource in:... which was fixed by falling back to the maven datasource (parses versions available in a package's
maven-metadata.xml
) if it failed to list registry directories in:I'm thinking the same fix should be applicable for the sbt-plugin datasource (I'm working on it, including reproduction).
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions