I wanted to clarify....that when I said Drush 12 is required for Drupal 10 I meant you need that version for D10. But, drush is not actually a requirement technically speaking, right? It just simplifies things by having a command line interface for the admin. So, if the guzzle version conflict is related to drush, then I believe I should be able to get rid of drush entirely from my account (at either root or site level or both)....then proceed with composer for managing the upgrade of sites to Drupal 10, and then reinstall Drush 12 at the site level. Does that seem a reasonable approach? Just simplify things from the current mixed up state?
I'm running into problems trying to install drush 12 locally (I currently have drush 10 globally), as part of my Drupal 9.5 to 10x upgrade. Drush 12 is required for Drupal 10, but Drush 12 also needs Guzzle 7.0. My current installation on Drupal 9.5.3 requires Guzzle 6.5.8. So it seems (?) that I can't simultaneously upgrade Guzzle to 7 on Drupal 9.5 and drush 12 in order to then use Drush 12 to do the upgrade to Drupal 10x. How can I install Drush 12 prior to upgrading to Drupal 10 when 9.5 requires Guzzle 6x and 10 requires Guzzle7x. Where/how is Guzzle updated from 6x to 7x in this process?
What am I missing here?
Problem 1
> - drush/drush[12.0.0, ..., 12.4.3] require guzzlehttp/guzzle ^7.0 -> found
> guzzlehttp/guzzle[7.0.0, ..., 7.8.1] but these were not loaded, likely
> because it conflicts with another require.
> - Root composer.json requires drush/drush 12.* -> satisfiable by
> drush/drush[12.0.0, ..., 12.4.3].
>
> Installation failed, reverting ./composer.json and ./composer.lock to
> their original content.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> jkstermi@chi-bnode2 [~/public_html/joestermitzphotography.com]# composer
> why-not guzzlehttp/guzzle ^7.8.1
> drupal/core-recommended 9.5.3 requires guzzlehttp/guzzle (~6.5.8)
> ###
>
> Please check your composer.lock file and ensure that your project is
> prepared for the update to Drush 12.