Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

MazeEzam's avatar

Blueprint - Laravel Shift

Hi, I have a new laravel install and I am attempting to install Blueprint "https://blueprint.laravelshift.com/"

When I run the installation command "composer require --dev laravel-shift/blueprint" I receive this error

"Your requirements could not be resolved to an installable set of packages. Problem 1 - laravel-shift/blueprint[0.1, ..., 0.5.1, 1.0.0, ..., v1.3.1] require symfony/yaml ^4.3 -> found symfony/yaml[v4.3.0, ..., v4.4.45] but the package is fixed to v7.0.0 (lock file version) by a partial update and that version does not match."

I'm new to Laravel so I am not sure if this is a newbie user issue or something else is broken within Blueprint?

Thanks in advance to any assistance.

0 likes
1 reply
LaryAI's avatar
Level 58

It looks like you're encountering a dependency version conflict. Blueprint requires a version of symfony/yaml that is compatible with ^4.3, but your Laravel installation is locked to symfony/yaml version v7.0.0. This is likely because the version of Laravel you are using requires symfony/yaml v7.0.0.

Here are the steps you can take to resolve this issue:

  1. Check your Laravel version to ensure it's compatible with the version of Blueprint you're trying to install. Blueprint may not yet be compatible with the latest Laravel version if it's very new.

  2. If your Laravel version is indeed compatible with Blueprint, you can try updating your composer.json to allow for the required version of symfony/yaml. However, this might cause other dependencies to break, so it's not the recommended approach unless you know what you're doing.

  3. The safest solution would be to install a version of Laravel that is compatible with Blueprint. You can check Blueprint's documentation or composer.json to see which versions of Laravel it supports.

  4. If you're set on using the current version of Laravel, you might need to wait for Blueprint to update their package to support symfony/yaml v7.0.0.

  5. As a last resort, you can fork the Blueprint repository, update the symfony/yaml dependency to v7.0.0, and then require your forked version in your composer.json. This is an advanced solution and should only be done if you're comfortable managing your own fork and dealing with any potential issues that arise.

Here's a general command to update a specific package using Composer, which you might use if you decide to update symfony/yaml:

composer update symfony/yaml --with-all-dependencies

Remember to always back up your code before making changes to your dependencies, as this can potentially break your application if not done carefully.

Please or to participate in this conversation.