-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Dependabot not able to find updates #408
Comments
Hey @DesignyourCode, I'm not really sure what to do about this or what Wpackagist could be doing wrong. Do you have a bit more background about how the process works, steps to replicate, etc.? As a quick initial check I loaded one of the Wpackagist URLs in your output. It includes a valid response with a valid version "4.8", normalised by Composer (v1)'s utility library as expected. And none of the 404s seem to be coming from Wpackagist itself. So: what is Dependabot expecting that it's not getting? And what exactly should Wpackagist be doing differently here? |
I have spoken with Github support about this issue. Dependabot is running on Composer 2. So the issue is that Wpackagist isn't supporting composer 2 yet. Or if it doesn't, it isn't fully supported. I have been given a line of code to add to the composer.lock which should solve this, but because the |
I can confirm that the above is the case. Wpackagist should support Composer 2. But as this is down to individual packages, it should look at heavily encouraging all packages to upgrade and support Composer 2. |
Hey @DesignyourCode – while addressing some more pressing security updates late last year, I upgraded Wpackagist to use Composer v2 internally. This promptly broke the service for all devs on Composer v1 who promptly let me know. After sorting this out (see #372, #373) we have the repository working, to my knowledge, fully on both v1 and v2. So we need to be pretty careful about the sense in which we are upgrading and how we go about it, and clear about what would have to change for this use of Dependabot to work. https://getcomposer.org/upgrade/UPGRADE-2.0.md lists a bunch of things we could add manually (presumably while maintaining v1 normalisation behaviour) but they all seem to be optional, and I'm still not clear which one(s) would help with this use case. Do you have any more details on what data would change and why to make this work? |
Hi @NoelLH thank you for your reply. I am still in discussions with Dependabot/Github Support regarding this. I am going to begin tests with Composer 2 to try and narrow down which settings or configuration options would be needed. I will feedback here with my conclusions and hopefully be able to provide some more detail. |
If you have any additional details here. That would be awesome. We've been working on our automation and this is something I investigated a while ago but haven't checked into it in a while. |
Hi @DesignyourCode - did you ever manage to get Dependabot working with wpackagist packages? I'd be really interested to hear the latest on this. Many thanks. |
👋 Hi from Dependabot. If there's anything we need to do from our side to support Re: There's no ETA as of now, and we're not in a hurry, but we will do it at some point. So if anyone watching this ticket will be impacted, please comment on ☝️ explaining what prevents you from updating to Composer v2. |
Hi. We are seeing issues in which Dependabot is unable to find updates for plugins.
We have raised a support issue with them, but from what I can see the issue would lie at Wpackagists end.
As you can see above, "Latest version is " returns blank, instead of returning a version number, which is what other packages return.
The text was updated successfully, but these errors were encountered: