andrey-helldar
commented
3 weeks ago @rtrudel, can you also show your localizations configuration file? It is located at the path config/localization.php. If you have it published.
Closed rtrudel closed 3 weeks ago
andrey-helldar
commented
3 weeks ago @rtrudel, can you also show your localizations configuration file? It is located at the path config/localization.php. If you have it published.
andrey-helldar
commented
3 weeks ago @rtrudel, that's it, don't. I found the reason. I'll fix it.
andrey-helldar
commented
3 weeks ago @rtrudel, I realized what the problem is - you have laravel-lang/models version v1.0-ALPHA1 installed. It was in it that you had this very migration file. There have been several more releases since then.
Can you run the console command composer info laravel-lang/models to make sure?
For example:
$ composer info laravel-lang/models
name : laravel-lang/models
descrip. : Easy and fast way to localize models
keywords : database, l18n, languages, laravel, locales, localization, models, translate, translations
versions : * 1.1.0Also, using the console command composer why laravel-lang/models you can find out if something is blocking the installation of the latest stable version of the package:
composer why laravel-lang/modelsLike this:
$ composer why laravel-lang/models
laravel-lang/common 6.4.0 requires laravel-lang/models (^1.0) 
rtrudel
commented
3 weeks ago $ composer info laravel-lang/models
name : laravel-lang/models
descrip. : Easy and fast way to localize models
keywords : database, l18n, languages, laravel, locales, localization, models, translate, translations
versions : * v1.0-ALPHA1$ composer why laravel-lang/models
laravel-lang/common 6.4.0 requires laravel-lang/models (^1.0) and why not dig a bit deeper into the rabbit hole?
$ composer why laravel-lang/common
laravel/laravel dev-main requires (for development) laravel-lang/common (^6.2) @rtrudel, I found a solution to your problem.
The reason is that the value of the minimum-stability parameter is not set as stable. This action has been recommended since Laravel 10.
To check, I changed the value of the parameter to dev and saw that my application installs DEV versions of dependencies, among them laravel-lang/models version v1.0-ALPHA1:
If you need a stable environment, I recommend replacing the value of the minimum-stability property in the composer.json file with stable and running the composer update console command. But in this case you will have to fix the version of the pestphp/pest-plugin-drift plugin to ^2.0 (it is currently listed as ^3.0 - this is an unstable version). And, after that, fix the other versions as well:
"require-dev": {
"fakerphp/faker": "^1.23",
"laravel-lang/common": "^6.2",
"laravel/pint": "^1.13",
"laravel/sail": "^1.29",
"mockery/mockery": "^1.6",
"nunomaduro/collision": "^8.0",
- "pestphp/pest": "^3.0",
- "pestphp/pest-plugin-drift": "^3.0",
+ "pestphp/pest": "^2.0",
+ "pestphp/pest-plugin-drift": "^2.0",
"spatie/laravel-error-solutions": "^1.0",
"spatie/laravel-ignition": "^2.4"
},If you need these dev dependencies, then explicitly specify the version "laravel-lang/models": "^1.1" in the composer.json file:
"require-dev": {
"fakerphp/faker": "^1.23",
"laravel-lang/common": "^6.4",
+ "laravel-lang/models": "^1.1",
"laravel/pint": "^1.13",
"laravel/sail": "^1.29",
"mockery/mockery": "^1.6",
"nunomaduro/collision": "^8.0",
"pestphp/pest": "^3.0",
"pestphp/pest-plugin-drift": "^3.0",
"spatie/laravel-error-solutions": "^1.0",
"spatie/laravel-ignition": "^2.4"
},After that, run the composer update console command.
But note that because of the minimum-stablility parameter, the dev versions of all packages including Laravel Lang: Models will also be installed. But this time a fresh version from the 1.x branch will be installed.
andrey-helldar
commented
3 weeks ago I don't know why, but Composer chose to install the ALPHA version of the package even though the minimum-stability parameter specifies dev (at least that's how I specified it for mine). This setting should have installed the dev version, not the alpha version. After all, to install alpha you have to specify - pay attention - alpha....
rtrudel
commented
3 weeks ago Thank you!
In the end, I just had to remove pestphp/pest-plugin-drift(which I don't need... I guess...) while keeping pestphp/pest at version 3.x, which is stable since few weeks I think.
"pestphp/pest": "^3.0",
- "pestphp/pest-plugin-drift": "^3.0"I also reinstalled laravel-lang/common, and there are no more pending migrations.
+ "laravel-lang/common": "^6.3"Pest 3 was set for release on September 9th. The pestphp/pest-plugin-drift plugin does not support it yet.
It is possible to downgrade the Laravel Lang Common version, but there is no point - the version is listed as ^6.3, which means that calling the composer update console command will install the latest version from line 6. At the moment it is 6.4.
Also, I still recommend setting the "minimum-stablility": "stable" parameter in the composer.json file and run the composer update console command after that.
Lang Package Name
laravel-lang/models
Lang Package Version
6.4.0
Laravel Framework Version
11.25.0
PHP Version
8.2
Dependencies
Issue description
Steps to reproduce
composer updatedoing some casual stuff in my appphp artisan migrate