Closed jesperbjerke closed 1 year ago
Just to be sure, have you tried a composer update --with-all-dependencies
?
Yes, no difference unfortunately.
$ composer update --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
$ composer outdated
kreait/firebase-php 6.8.0 6.9.1 Firebase Admin SDK
That's really weird - I was able to reproduce the issue in a fresh directory with the contents of your composer.json - only the 6.8 release was installed.
I then did a composer show | grep kreait
and a composer why kreait/firebase-php
and saw no reason why it shouldn't install the latest version:
❯ composer show | grep kreait
kreait/firebase-php 6.8.0 Firebase Admin SDK
kreait/firebase-tokens 3.0.3 A library to work w...
kreait/laravel-firebase 4.2.0 A Laravel package f...
❯ composer why kreait/firebase-php
kreait/laravel-firebase 4.2.0 requires kreait/firebase-php (^6.7)
What's even weirder - once I did a composer require -W "kreait/firebase-php:^6.9.1"
, it installed the latest version of the SDK. But why, I don't know.
Anyway, this resolved the issue for me, let me know if it does for you as well.
But don't try to remove the explicit dependency from your composer.json afterwards again, this will install the older release again. Super weird!
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let me know if that works for you by leaving a 👍. Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
Sorry, forgot to update the issue. Yes, installing the peer dependency manually forced the newer version to get installed. Havent had time to investigate the root cause yet, but so far it seems to be an okay work-around.
Describe the bug
So this is a weird thing. This might not be an issue of this package, and just something with my configuration. But I have this issue in 2 different projects, one with php 7.4 and Laravel 8 and one with php 8.1 and Laravel 9. Since the last two minor versions of the
firebase-php
package, composer won't update and we are stuck on6.8.0
. We do not have this package added as a root package, so it's only installed throughlaravel-firebase
. I cannot find anything blocking this update. Tryingcomposer why-not
does not report any blocker either.Any idea why this is? Have not had this issue before, and it seems to only be an issue with
firebase-php
.Installed packages
Steps to reproduce the issue.
Just run
composer update
and thencomposer outdated
still says we're on version6.8.0
of firebase-php and that6.9.1
is available.Error message/Stack trace
Additional information
No response