laravel / passport

Laravel Passport provides OAuth2 server support to Laravel.

Home Page:https://laravel.com/docs/passport

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Package version conflicts when installing Passport in a clean Laravel 10 project

binaryfire opened this issue · comments

Passport Version

11.8.1

Laravel Version

10.13.2

PHP Version

8.2.6

Database Driver & Version

8.0.33 (Ubuntu 22.04 / WSL2)

Description

I'm getting this error when trying to require Passport in a new Laravel 10 project:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - laravel/passport[v11.8.5, ..., v11.8.7] require league/oauth2-server ^8.5.1 -> satisfiable by league/oauth2-server[8.5.1].
    - laravel/passport[v11.8.0, ..., v11.8.4] require league/oauth2-server ^8.2 -> satisfiable by league/oauth2-server[8.2.0, ..., 8.5.1].
    - league/oauth2-server[8.2.0, ..., 8.5.1] require psr/http-message ^1.0.1 -> found psr/http-message[1.0.1, 1.1] but the package is fixed to 2.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires laravel/passport ^11.8 -> satisfiable by laravel/passport[v11.8.0, ..., v11.8.7].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require laravel/passport:*" to figure out if any version is installable, or "composer require laravel/passport:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I'm not sure what's going on, because v2.0 of http-message should work with league/oauth2-server: composer.json

Steps To Reproduce

laravel new passport-test
cd passport-test
composer require laravel/passport

Will be fixed once thephpleague/oauth2-server#1339 is released.

@driesvints Ah, that’s a recent bump that hasn’t been tagged yet. I missed that.

Thanks!

@binaryfire release now tagged 👍

news here? have the same error.