Hey Dude !
Thanks for you're work.
It seem that updates broke this bundle :
`➜ project git:(main) ✗ composer require manuxi/google-reviews-bundle
./composer.json has been updated
Running composer update manuxi/google-reviews-bundle
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires manuxi/google-reviews-bundle * -> satisfiable by manuxi/google-reviews-bundle[v1.0.0, v1.0.1, v1.0.2, v1.0.3].
- manuxi/google-reviews-bundle v1.0.0 requires symfony/config ^4.0 || ^5.0 -> found symfony/config[v4.0.0, ..., v4.4.44, v5.0.0, ..., v5.4.46] but the package is fixed to v7.3.6 (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.
- manuxi/google-reviews-bundle[v1.0.1, ..., v1.0.3] require symfony/config ^4.0 || ^5.0 || ^6.0 -> found symfony/config[v4.0.0, ..., v4.4.44, v5.0.0, ..., v5.4.46, v6.0.0, ..., v6.4.28] but the package is fixed to v7.3.6 (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.
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 manuxi/google-reviews-bundle:*" to figure out if any version is installable, or "composer require manuxi/google-reviews-bundle:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
`
Hey Dude !
Thanks for you're work.
It seem that updates broke this bundle :
`➜ project git:(main) ✗ composer require manuxi/google-reviews-bundle
./composer.json has been updated
Running composer update manuxi/google-reviews-bundle
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires manuxi/google-reviews-bundle * -> satisfiable by manuxi/google-reviews-bundle[v1.0.0, v1.0.1, v1.0.2, v1.0.3].
- manuxi/google-reviews-bundle v1.0.0 requires symfony/config ^4.0 || ^5.0 -> found symfony/config[v4.0.0, ..., v4.4.44, v5.0.0, ..., v5.4.46] but the package is fixed to v7.3.6 (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.
- manuxi/google-reviews-bundle[v1.0.1, ..., v1.0.3] require symfony/config ^4.0 || ^5.0 || ^6.0 -> found symfony/config[v4.0.0, ..., v4.4.44, v5.0.0, ..., v5.4.46, v6.0.0, ..., v6.4.28] but the package is fixed to v7.3.6 (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.
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 manuxi/google-reviews-bundle:*" to figure out if any version is installable, or "composer require manuxi/google-reviews-bundle:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
`