Closed jcolfej closed 4 years ago
After some tests, this problem is only in case if you use S3 as blobstore. Maybe a problem due to AWS S3 async process ?
That is interesting. @fjmilens3 or @ataylor284 might be interested.
I have the exact same problem and I dont use S3 as blobstore, just "default" blob storage type. I have posted on this issue few days ago because I thought the "Rebuild All Composer MetaData task" could solve this but if this task intend to do the same thing as the "Rebuild Index" button in the repo's admin panel, then it wont work. @fjmilens3 @TheBay0r Could you guys tell us what could cause this ?
Any news on this issue ? Please could someone point us why it does not update the JSON ? It's really a pity because it is the last small issue that prevents me from using this full-scale.... @DarthHater @ataylor284 @fjmilens3 Are you okay man ? 4 months without ANY commits makes me worry.
I ran into the same problem. But I found solution, in settings of composer-hosted repository you should allow redeploy.
@bcastagna sadly @fjmilens3 has moved on to greener pastures from Sonatype, which doesn't mean he won't pop back in here, but it would be out of the kindness of his big heart (he has one for sure). I've been fairly busy helping get another person scaled up on working on this type of stuff, and we are working through a backlog on some other issues right now. I'll try and get either @bhamail or myself to pop in here some time soon!
hi guys, i have the same problem, is there any update to tetram's pr ?
Encountered
I ran into the same problem. But I found solution, in settings of composer-hosted repository you should allow redeploy.
+++
This is quite a critical issue imho
"Allow redeploy" is a very dangerous settings because it allows packages to be overwritten if an update is made but the version is not increased :
composer install
will always fail because package sha changed.I merged PR #44 from @tetram. Please give it a try and report any issues.
I try to add new versions of my package on a hosted composer repo. New versions don't appear on
https://my.nexus/repository/composer_hosted/p/vendor/package.json
... I only have my first package version.Currently, I push a 1.0.0 version and few minutes after, I push 1.0.1, but json say :
Is anyone have same problem ?