Closed mtx-z closed 8 months ago
Having the same issue. Laravel 10.10.1
Looks like the problem is that SimpleAnnotationReader
was dropped in doctrine/annotations
2.0 (https://github.com/doctrine/annotations/issues/232), but dingo/blueprint
is still using it (https://github.com/dingo/blueprint/blob/master/src/Blueprint.php#LL53C1-L53C1)
I have the same problem here. I update version 9 to 10 of Laravel. The solution "adding to your composer.json: "dingo/blueprint": "0.4.5"" doesn't work because still install the version 0.4.6... :/
@TSerra-PT are you sure that you don't have another package requiring dingo/blueprint? Adding the strict 0.4.5 version should work after a composer update
.
@mtx-z In composer.json i have the version 0.4.5, but it install the 0.46.... :/
I'm double checking but are you sure you're doing a "composer update"? As composer install may install 0.4.6 from lock.
@mtx-z yes...
Strange. You can try delete lock file (and vendor?) then composer install again. It worked from my end.
I can confirm this issue, the update for blueprint latest (0.4.6) isn't enough, because not only should doctrine/annotations be updated to 2, but I think the code needs to also be updated.
I will comment out the registration of the blueprint cli command for the time being and tag as a bugfix, until it's resolved in blueprint.
If anyone is using the blueprint package, please take a look at it - personally I have not been using it.
Tagged as v4.1.1 - but I'll keep this open as an ongoing issue, especially if anyone encounters it they can check here.
@mtx-z delete lock file and vendor did the trick. thanks!
Another solution is it to lock "doctrine/annotations" in tag 1.14.3, the latest version before 2.0 was published. Because of the composer.json in "dingo/blueprint@0.4.5" requires "doctrine/annotations": "~1.2 ", while "dingo/blueprint@0.4.6" requires "doctrine/annotations": "~1.2 | ^2.0". is what created this issue.
Locking "doctrine/annotations": "v1.14.3" in the composer.json file, delete the lock file and a composer update did the trick.
^ With above, keep in mind that v1 of doctrine/annotations doesn't support PHP 8, hence why that dep was updated in the first place.
Actual Behaviour
I had an error when doing a
composer update
:This seems to be caused by the recent (14/05/2023)
dingo\blueprint
0.4.6 update, required byapi-ecosystem-for-laravel
(as"dingo/blueprint": "^0.4.5"
).Possible Solutions
Switch back to the previous
dingo\blueprint
version, adding to yourcomposer.json
:"dingo/blueprint": "0.4.5"
Should I report this to dingo\blueprint ? This issue may be related.