Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended 11.0.x-dev requires drupal/core 11.0.x-dev -> found drupal/core[11.0.x-dev] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.x-dev requires drupal/core 11.x-dev -> found drupal/core[11.x-dev] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-alpha1 requires drupal/core 11.0.0-alpha1 -> found drupal/core[11.0.0-alpha1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-beta1 requires drupal/core 11.0.0-beta1 -> found drupal/core[11.0.0-beta1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-rc1 requires drupal/core 11.0.0-rc1 -> found drupal/core[11.0.0-rc1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> found drupal/core[11.0.0] but it conflicts with your root composer.json require (^10.1). - Root composer.json requires drupal/core-recommended ^11.0 -> satisfiable by drupal/core-recommended[11.0.0-alpha1, ..., 11.x-dev]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires drupal/core ^10.1, found drupal/core[10.1.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 2 - Root composer.json requires drupal/colorbox 2.0.2 -> satisfiable by drupal/colorbox[2.0.2]. - drupal/colorbox 2.0.2 requires drupal/core ^8.8 || ^9 || ^10 -> found drupal/core[8.8.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 3 - Root composer.json requires drupal/dropzonejs 2.8 -> satisfiable by drupal/dropzonejs[2.8.0]. - drupal/dropzonejs 2.8.0 requires drupal/core ^9.3 || ^10 -> found drupal/core[9.3.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 4 - Root composer.json requires drupal/field_group 3.4 -> satisfiable by drupal/field_group[3.4.0]. - drupal/field_group 3.4.0 requires drupal/core ^9.2 || ^10 -> found drupal/core[9.2.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 5 - Root composer.json requires drupal/oembed_lazyload ^2.0 -> satisfiable by drupal/oembed_lazyload[2.0.0, ..., 2.1.x-dev]. - drupal/oembed_lazyload[2.0.0, ..., 2.1.x-dev] require drupal/core ^9 || ^10 -> found drupal/core[9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 6 - Root composer.json requires drupal/subrequests 3.0.11 -> satisfiable by drupal/subrequests[3.0.11]. - drupal/subrequests 3.0.11 requires drupal/core ^8 || ^9 || ^10 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 7 - Root composer.json requires su-sws/stanford_profile 11.x-dev -> satisfiable by su-sws/stanford_profile[11.x-dev]. - su-sws/stanford_profile 11.x-dev requires drupal/core ~10.3.0 -> found drupal/core[10.3.0-beta1, ..., 10.3.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 8 - drupal/core 11.0.0 requires php >=8.3.0 -> your php version (8.2.21) does not satisfy that requirement. - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> satisfiable by drupal/core[11.0.0]. - drupal/core-recommended is locked to version 11.0.0 and an update of this package was not requested. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 127.

Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended 11.0.x-dev requires drupal/core 11.0.x-dev -> found drupal/core[11.0.x-dev] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.x-dev requires drupal/core 11.x-dev -> found drupal/core[11.x-dev] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-alpha1 requires drupal/core 11.0.0-alpha1 -> found drupal/core[11.0.0-alpha1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-beta1 requires drupal/core 11.0.0-beta1 -> found drupal/core[11.0.0-beta1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-rc1 requires drupal/core 11.0.0-rc1 -> found drupal/core[11.0.0-rc1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> found drupal/core[11.0.0] but it conflicts with your root composer.json require (^10.1). - Root composer.json requires drupal/core-recommended ^11.0 -> satisfiable by drupal/core-recommended[11.0.0-alpha1, ..., 11.x-dev]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires drupal/core ^10.1, found drupal/core[10.1.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 2 - Root composer.json requires drupal/colorbox 2.0.2 -> satisfiable by drupal/colorbox[2.0.2]. - drupal/colorbox 2.0.2 requires drupal/core ^8.8 || ^9 || ^10 -> found drupal/core[8.8.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 3 - Root composer.json requires drupal/dropzonejs 2.8 -> satisfiable by drupal/dropzonejs[2.8.0]. - drupal/dropzonejs 2.8.0 requires drupal/core ^9.3 || ^10 -> found drupal/core[9.3.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 4 - Root composer.json requires drupal/field_group 3.4 -> satisfiable by drupal/field_group[3.4.0]. - drupal/field_group 3.4.0 requires drupal/core ^9.2 || ^10 -> found drupal/core[9.2.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 5 - Root composer.json requires drupal/oembed_lazyload ^2.0 -> satisfiable by drupal/oembed_lazyload[2.0.0, ..., 2.1.x-dev]. - drupal/oembed_lazyload[2.0.0, ..., 2.1.x-dev] require drupal/core ^9 || ^10 -> found drupal/core[9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 6 - Root composer.json requires drupal/subrequests 3.0.11 -> satisfiable by drupal/subrequests[3.0.11]. - drupal/subrequests 3.0.11 requires drupal/core ^8 || ^9 || ^10 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 7 - Root composer.json requires su-sws/stanford_profile 11.x-dev -> satisfiable by su-sws/stanford_profile[11.x-dev]. - su-sws/stanford_profile 11.x-dev requires drupal/core ~10.3.0 -> found drupal/core[10.3.0-beta1, ..., 10.3.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 8 - drupal/core 11.0.0 requires php >=8.3.0 -> your php version (8.2.21) does not satisfy that requirement. - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> satisfiable by drupal/core[11.0.0]. - drupal/core-recommended is locked to version 11.0.0 and an update of this package was not requested. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 127.

Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended 11.0.x-dev requires drupal/core 11.0.x-dev -> found drupal/core[11.0.x-dev] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.x-dev requires drupal/core 11.x-dev -> found drupal/core[11.x-dev] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-alpha1 requires drupal/core 11.0.0-alpha1 -> found drupal/core[11.0.0-alpha1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-beta1 requires drupal/core 11.0.0-beta1 -> found drupal/core[11.0.0-beta1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0-rc1 requires drupal/core 11.0.0-rc1 -> found drupal/core[11.0.0-rc1] but it conflicts with your root composer.json require (^10.1). - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> found drupal/core[11.0.0] but it conflicts with your root composer.json require (^10.1). - Root composer.json requires drupal/core-recommended ^11.0 -> satisfiable by drupal/core-recommended[11.0.0-alpha1, ..., 11.x-dev]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires drupal/core ^10.1, found drupal/core[10.1.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 2 - Root composer.json requires drupal/colorbox 2.0.2 -> satisfiable by drupal/colorbox[2.0.2]. - drupal/colorbox 2.0.2 requires drupal/core ^8.8 || ^9 || ^10 -> found drupal/core[8.8.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 3 - Root composer.json requires drupal/dropzonejs 2.8 -> satisfiable by drupal/dropzonejs[2.8.0]. - drupal/dropzonejs 2.8.0 requires drupal/core ^9.3 || ^10 -> found drupal/core[9.3.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 4 - Root composer.json requires drupal/field_group 3.4 -> satisfiable by drupal/field_group[3.4.0]. - drupal/field_group 3.4.0 requires drupal/core ^9.2 || ^10 -> found drupal/core[9.2.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 5 - Root composer.json requires drupal/oembed_lazyload ^2.0 -> satisfiable by drupal/oembed_lazyload[2.0.0, ..., 2.1.x-dev]. - drupal/oembed_lazyload[2.0.0, ..., 2.1.x-dev] require drupal/core ^9 || ^10 -> found drupal/core[9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 6 - Root composer.json requires drupal/subrequests 3.0.11 -> satisfiable by drupal/subrequests[3.0.11]. - drupal/subrequests 3.0.11 requires drupal/core ^8 || ^9 || ^10 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.4.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 7 - Root composer.json requires su-sws/stanford_profile 11.x-dev -> satisfiable by su-sws/stanford_profile[11.x-dev]. - su-sws/stanford_profile 11.x-dev requires drupal/core ~10.3.0 -> found drupal/core[10.3.0-beta1, ..., 10.3.x-dev] but the package is fixed to 11.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. Problem 8 - drupal/core 11.0.0 requires php >=8.3.0 -> your php version (8.2.21) does not satisfy that requirement. - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> satisfiable by drupal/core[11.0.0]. - drupal/core-recommended is locked to version 11.0.0 and an update of this package was not requested. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 127.

No files were found with the provided path: /var/www/html/artifacts. No artifacts will be uploaded.

No files were found with the provided path: /var/www/html/artifacts. No artifacts will be uploaded.