You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✗ composer require awssat/laravel-sync-migration
./composer.json has been updated
Running composer update awssat/laravel-sync-migration
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- awssat/laravel-sync-migration[0.1, ..., 0.1.3] require php ~5.6|~7.0 -> your php version (8.1.27) does not satisfy that requirement.
- awssat/laravel-sync-migration[0.1.4, ..., 0.2.0] require php ~7.1 -> your php version (8.1.27) does not satisfy that requirement.
- awssat/laravel-sync-migration[v3.0, ..., v3.0.1] require illuminate/support 5.0 - 5.8 | ^6.0 | ^7.0 | ^8.0 -> found illuminate/support[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- awssat/laravel-sync-migration 4.0.0 requires illuminate/support ~5.5.0 ||~5.6.0 ||~5.7.0 ||~5.8.0 || ^6.0 || ^7.0 || ^8.0 || ^9.0 -> found illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires awssat/laravel-sync-migration * -> satisfiable by awssat/laravel-sync-migration[0.1, ..., 0.2.0, v3.0, v3.0.1, 4.0.0].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require awssat/laravel-sync-migration:*" to figure out if any version is installable, or "composer require awssat/laravel-sync-migration:^2.1"if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: