Closed aldobarr closed 5 months ago
Hi @aldobarr,
From the logs it's not quite apparent what is wrong with the installation. We haven't done any changes to the build system at all.
I've check the build and release logs, I've detected no anomaly.
I couldn't tell you what the issue is. The actual usage for us is with the l5-swagger package for laravel. Our container is configured to update packages with dependencies on startup via:
composer update -W
This started happening today which coincides with the 5.17.0 release
Could you setup a small repo for me to reproduce the issue there?
Nevermind, this is my fault I see the issue now is permission related. Not sure how permissions changed but got this resolved. Sorry for the false alarm.
For reference here is a composer release log: https://jenkins.swagger.io/view/OSS%20-%20JavaScript%20Releases/job/oss-swagger-api-packagist-trigger/212/console
Q&A (please complete the following information)
Describe the bug you're encountering
composer update
today is causing the docker container to no longer start due to failures with the update. See log:To reproduce...
Update via composer to today's release
Expected behavior
Update should not break.