-
Notifications
You must be signed in to change notification settings - Fork 1
Unable to pull high version #8
Comments
Hi! Thanks for the report; could you share your Velocita config and |
Velocita config:
composer.json
Things like |
Could you try to add the following Velocita setting and let me know if that resolves the issue?
If that works, I might need to update the default value for this. I think it was introduced because Packagist used to generate unique package JSON URLs between updates, but they no longer do so with the p2 version of their URL scheme. |
But my visit to |
Please try my suggestion regardless; Composer might send a different request than your manual one. |
OK, I modified the I tried using Some of the logs are as follows
The version was rolled back. Meanwhile, my browser opens up to
|
Thanks for all the information and apologies for the delay in coming back to you - I've been trying on and off to replicate your issue but have been unable to do so. Are you able to provide reproduction steps starting with a new Velocita instance? |
Hello!
I'm having a problem with it. At the time of my posting, the highest version of
symfony/cache
that matches my environment is v6.4.2, but when I go to update it via velocita, I keep getting v6.4.0.I tried to access
https://VELOCITA_URL/mirror/packagist/p2/symfony/cache.json
and there is v6.4.2 version info in there!Of course I tried to use
composer update symfony/cache --no-cache
to update it, but still can't get the high version.for example:
When I turn off
composer velocita:disable
, I can update to v6.4.2 normally!What should I do?
The text was updated successfully, but these errors were encountered: