- Issue created by @YuvalBH
- First commit to issue fork.
Hi @yuvalbh,
I tried to recreate this issue by following your steps, but could not replicate it.Steps followed to reproduce
- made a fresh drupal 10.3.1 site installation. Attached the screen shot for the system info.
- Updated to drupal version 10.4.0, following from
Drupal update document →
applied this command to update the
composer require drupal/core-recommended:10.4.0 drupal/core-composer-scaffold:10.4.0 drupal/core-project-message:10.4.0 --update-with-all-dependencies
then
drush updb
followed bydrush cr
. Attaching a screen shot for the system info.
Please provide more info to reproduce the issue.
- 🇮🇳India mdsohaib4242
You could try checking for any existing conflicts in composer.json
composer why guzzlehttp/guzzle
If a specific package is requiring an incompatible version of Guzzle, update it to a version that is compatible with guzzlehttp/guzzle ~7.9.2 or you could Temporarily remove conflicting dependencies then proceed with the Drupal upgrade.
If there are no conflicting packages
composer require guzzlehttp/guzzle:~7.9.2 --update-with-all-dependencies
Then retry the upgrade command for Drupal core.
- 🇬🇧United Kingdom longwave UK
We need more information to be able to reproduce this.
- 🇮🇱Israel YuvalBH
issue solved:
The old aws/aws-sdk-php was set to be with guzzlehttp/guzzle version 7.8.2, after updating aws issue solved.command:
composer require aws/aws-sdk-php --update-with-all-dependenciesin order to reproduce issue you need to have: aws/aws-sdk-php v3.316.9
updating aws/aws-sdk-php (3.316.9 => 3.336.13)check your aws/aws-sdk-php with command: composer show aws/aws-sdk-php