Update composer.lock
by running composer update
#32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tl;dr: #31 only updated
composer.json
but notcomposer.lock
.I noticed that the
composer.lock
was outdated, which leads to the problem thatopencensus/opencensus
is still locked tov0.5.2
instead ofv0.7.0
, thus making this package incompatible with modern Laravel versions. This probably explains why another user was reporting a problem using this package with Laravel 8 (sadly the issue was still closed): #26 (comment)See the listed requirements of
0.2.2
of this package on packagist: https://packagist.org/packages/gluedev/laravel-stackdriverversus the current
composer.json
: a294a2aYou can also verify this by cloning the current state (at the time of writing
a294a2a429cf5d0352d542d836fea4f97ff7c68a
) and runcomposer install
. It will give you an output like this:Composer version used for this PR: 2.6.5 2023-10-06 10:11:52
Command used for this PR:
docker run -it --rm --user $(id -u):$(id -g) -v ~/.composer:/tmp -v $(pwd):/app docker.io/composer update --ignore-platform-reqs