F
Filament•3mo ago
OzgurOzarpaci

Can't Upgrade my Filament because of Depencies

Hi, I have a project and Filament Stucks at 3.2.0 version and I can't use cache components commands. Because composer says this:
Solution:
There it is. All of your spatie filament packages are locked to 3.2. Change those to ^3.2 and run composer update.
Jump to solution
17 Replies
OzgurOzarpaci
OzgurOzarpaci•3mo ago
$ composer require filament/filament:"3.2.67"

./composer.json has been updated
Running composer update filament/filament
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 filament/filament 3.2.67 (exact version match: 3.2.67 or 3.2.67.0), found filament/filament[dev-3.x-alpha, v0.1.0, v1.0.0, ..., 1.x-dev, v2.0.0-beta1, ..., 2.x-dev, v3.0.0-alpha1, ..., 3.x-dev] but it does not match the constraint.
  Problem 2
    - althinect/filament-spatie-roles-permissions is locked to version v2.2.23 and an update of this package was not requested.
    - althinect/filament-spatie-roles-permissions v2.2.23 requires filament/filament ^3.0 -> found filament/filament[v3.0.0-alpha1, ..., 3.x-dev] but it conflicts with your root composer.json require (3.2.67).
$ composer require filament/filament:"3.2.67"

./composer.json has been updated
Running composer update filament/filament
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 filament/filament 3.2.67 (exact version match: 3.2.67 or 3.2.67.0), found filament/filament[dev-3.x-alpha, v0.1.0, v1.0.0, ..., 1.x-dev, v2.0.0-beta1, ..., 2.x-dev, v3.0.0-alpha1, ..., 3.x-dev] but it does not match the constraint.
  Problem 2
    - althinect/filament-spatie-roles-permissions is locked to version v2.2.23 and an update of this package was not requested.
    - althinect/filament-spatie-roles-permissions v2.2.23 requires filament/filament ^3.0 -> found filament/filament[v3.0.0-alpha1, ..., 3.x-dev] but it conflicts with your root composer.json require (3.2.67).
   
  Problem 4
    - filament/spatie-laravel-settings-plugin is locked to version v3.2.0 and an update of this package was not requested.
    - filament/spatie-laravel-settings-plugin v3.2.0 requires filament/filament v3.2.0 -> found filament/filament[v3.2.0] but it conflicts with your root composer.json require (3.2.67).
  Problem 5
    - shuvroroy/filament-spatie-laravel-backup is locked to version v2.1.3 and an update of this package was not requested.
    - shuvroroy/filament-spatie-laravel-backup v2.1.3 requires filament/filament ^3.0 -> found filament/filament[v3.0.0-alpha1, ..., 3.x-dev] but it conflicts with your root composer.json require (3.2.67).
  Problem 6
    - shuvroroy/filament-spatie-laravel-health is locked to version v2.0.1 and an update of this package was not requested.
    - shuvroroy/filament-spatie-laravel-health v2.0.1 requires filament/filament ^3.0 -> found filament/filament[v3.0.0-alpha1, ..., 3.x-dev] but it conflicts with your root composer.json require (3.2.67).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
   
  Problem 4
    - filament/spatie-laravel-settings-plugin is locked to version v3.2.0 and an update of this package was not requested.
    - filament/spatie-laravel-settings-plugin v3.2.0 requires filament/filament v3.2.0 -> found filament/filament[v3.2.0] but it conflicts with your root composer.json require (3.2.67).
  Problem 5
    - shuvroroy/filament-spatie-laravel-backup is locked to version v2.1.3 and an update of this package was not requested.
    - shuvroroy/filament-spatie-laravel-backup v2.1.3 requires filament/filament ^3.0 -> found filament/filament[v3.0.0-alpha1, ..., 3.x-dev] but it conflicts with your root composer.json require (3.2.67).
  Problem 6
    - shuvroroy/filament-spatie-laravel-health is locked to version v2.0.1 and an update of this package was not requested.
    - shuvroroy/filament-spatie-laravel-health v2.0.1 requires filament/filament ^3.0 -> found filament/filament[v3.0.0-alpha1, ..., 3.x-dev] but it conflicts with your root composer.json require (3.2.67).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I looked at the packages and they are support filament ^3.2 and I don't know what to do 😦
Lara Zeus
Lara Zeus•3mo ago
try composer update --with-all-dependencies
OzgurOzarpaci
OzgurOzarpaci•3mo ago
It's not updated filament again 😦
No description
No description
LeandroFerreira
LeandroFerreira•3mo ago
"minimum-stability": "stable",
"prefer-stable": true
"minimum-stability": "stable",
"prefer-stable": true
?
OzgurOzarpaci
OzgurOzarpaci•3mo ago
This is not worked neither 😦 My composer file is looks like this (partially): 
"php": "^8.2",
"althinect/filament-spatie-roles-permissions": "*",
"awcodes/shout": "^2.0",
"bezhansalleh/filament-google-analytics": "^2.0",
"filament/spatie-laravel-media-library-plugin": "3.2",
"filament/spatie-laravel-settings-plugin": "3.2",
"filament/spatie-laravel-tags-plugin": "3.2",
"filament/spatie-laravel-translatable-plugin": "3.2",
"livewire/livewire": "^3.0",
"shuvroroy/filament-spatie-laravel-backup": "^2.1",
"shuvroroy/filament-spatie-laravel-health": "*",
"filament/filament": "^3.2"
"php": "^8.2",
"althinect/filament-spatie-roles-permissions": "*",
"awcodes/shout": "^2.0",
"bezhansalleh/filament-google-analytics": "^2.0",
"filament/spatie-laravel-media-library-plugin": "3.2",
"filament/spatie-laravel-settings-plugin": "3.2",
"filament/spatie-laravel-tags-plugin": "3.2",
"filament/spatie-laravel-translatable-plugin": "3.2",
"livewire/livewire": "^3.0",
"shuvroroy/filament-spatie-laravel-backup": "^2.1",
"shuvroroy/filament-spatie-laravel-health": "*",
"filament/filament": "^3.2"
awcodes
awcodes•3mo ago
Do you have forked versions of the packages that you have set to “*”? I’m guessing those are the problem since they are looking for a dev-main branch that may not be suitable for production use. And could have locked down versions in their own dependencies.
OzgurOzarpaci
OzgurOzarpaci•3mo ago
I don't change the versions, I just use install commands from documentations. I am trying change now I will inform you.
awcodes
awcodes•3mo ago
I doubt the install instructions for those two packages have a * for the version number.
OzgurOzarpaci
OzgurOzarpaci•3mo ago
I get that but why even your package Shout is giving this: Problem 3 - awcodes/shout is locked to version v2.0.3 and an update of this package was not requested. - awcodes/shout v2.0.3 requires filament/filament ^3.0 -> found filament/filament[v3.0.0, ..., v3.2.62] but it conflicts with your root composer.json require (3.2.67).
awcodes
awcodes•3mo ago
Because something in your dependencies is locking filament to a specific version.
OzgurOzarpaci
OzgurOzarpaci•3mo ago
I don't know why but all updated their las version but filament not updated
No description

composer.json

awcodes
awcodes•3mo ago
Also, the latest version of filament is 3.2.62, so yea 3.2.67 doesn’t even exist.
OzgurOzarpaci
OzgurOzarpaci•3mo ago
Sorry I wrote that wrong but with 62 it's still giving the same error 🥲
awcodes
awcodes•3mo ago
One of your packages is broken.
OzgurOzarpaci
OzgurOzarpaci•3mo ago
I am searching for which one. I will delete all flament packages first and update filament
Solution
awcodes
awcodes•3mo ago
There it is. All of your spatie filament packages are locked to 3.2. Change those to ^3.2 and run composer update.
OzgurOzarpaci
OzgurOzarpaci•3mo ago
Oh sh*t! I think your are right It's updating packages ❤️ I really didn't see that detail 😄 Thank you so much you saved my day ❤️
Want results from more Discord servers?
Add your server
More Posts
Renderhook Cannot Received Dispatched EventHello, I am using a renderhook to include some custom JS on a specific page using: ``` FilamentVieRelationshipManager refresh after editafter edit null field getting errorAccessing $request vars in observerSo I ran into this problem multiple times but always changed it differently. I'm now posting this hoDynamically create a column in the```php Tables\Columns\TextColumn::make('date') ->date() The form fields are not mounted into the edit formI am using standalone filament tables builder. Here is the ProductTable component which use as a LiHow to customize sidebar collapse iconI thought I had read about this in the doc previously but I can't seem to find it anywhere. Is thereI can't select the first index. I've been banging my head for hours.Reference 1: https://www.youtube.com/watch?v=Bcb_A9Sk78s Reference 2: https://github.com/andrewdwallThe POST method is not supported for route admin/login. Supported methods: GET, HEAD.Hi, I have this problem when i want to login.Uncaught (in promise) TypeError: Cannot read properties of null (reading 'insertBefore')Hi, Did you seen this error when you used FileUpload::imageEditor ? When I click on the pencil, notdark mode in form livewire componentHi, i want to ask how to make a dark mode or auto color theme in livewire component. My Livewire com