Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires su-sws/stanford_profile ^11.0 -> satisfiable by su-sws/stanford_profile[11.0.0, ..., 11.x-dev]. - drupal/core-recommended 10.3.0-beta1 requires drupal/core 10.3.0-beta1 -> satisfiable by drupal/core[10.3.0-beta1]. - Conclusion: don't install drupal/core 10.3.0-beta1 (conflict analysis result) - drupal/core-recommended 10.3.0-rc1 requires drupal/core 10.3.0-rc1 -> satisfiable by drupal/core[10.3.0-rc1]. - Conclusion: don't install drupal/core 10.3.0-rc1 (conflict analysis result) - drupal/core-recommended 10.3.0 requires drupal/core 10.3.0 -> satisfiable by drupal/core[10.3.0]. - Conclusion: don't install drupal/core 10.3.0 (conflict analysis result) - drupal/core-recommended 10.3.1 requires drupal/core 10.3.1 -> satisfiable by drupal/core[10.3.1]. - Conclusion: don't install drupal/core 10.3.1 (conflict analysis result) - drupal/core-recommended 10.4.x-dev requires drupal/core 10.4.x-dev -> satisfiable by drupal/core[10.4.x-dev]. - drupal/core-recommended 10.3.x-dev requires drupal/core 10.3.x-dev -> satisfiable by drupal/core[10.3.x-dev]. - You can only install one version of a package, so only one of these can be installed: drupal/core[10.1.0-alpha1, ..., 10.4.x-dev]. - Conclusion: install drupal/core 10.2.x-dev (conflict analysis result) - Root composer.json requires drupal/core-recommended ^10.3 -> satisfiable by drupal/core-recommended[10.3.0-beta1, ..., 10.4.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 - su-sws/stanford_profile 11.x-dev requires drupal/diff ^1.3 -> found drupal/diff[dev-1.x, 1.3.0, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (1.1). - su-sws/stanford_profile[11.0.0, ..., 11.1.0] require drupal/address ^1.2 -> found drupal/address[dev-1.x, 1.2.0, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (^2.0). - su-sws/stanford_profile[11.2.0, ..., 11.3.8] require drupal/core ~10.2.0 -> found drupal/core[10.2.0-alpha1, ..., 10.2.x-dev] but the package is fixed to 10.3.1 (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. - Root composer.json requires su-sws/stanford_profile ^11.0 -> satisfiable by su-sws/stanford_profile[11.0.0, ..., 11.x-dev]. 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 - Root composer.json requires su-sws/stanford_profile ^11.0 -> satisfiable by su-sws/stanford_profile[11.0.0, ..., 11.x-dev]. - drupal/core-recommended 10.3.0-beta1 requires drupal/core 10.3.0-beta1 -> satisfiable by drupal/core[10.3.0-beta1]. - Conclusion: don't install drupal/core 10.3.0-beta1 (conflict analysis result) - drupal/core-recommended 10.3.0-rc1 requires drupal/core 10.3.0-rc1 -> satisfiable by drupal/core[10.3.0-rc1]. - Conclusion: don't install drupal/core 10.3.0-rc1 (conflict analysis result) - drupal/core-recommended 10.3.0 requires drupal/core 10.3.0 -> satisfiable by drupal/core[10.3.0]. - Conclusion: don't install drupal/core 10.3.0 (conflict analysis result) - drupal/core-recommended 10.3.1 requires drupal/core 10.3.1 -> satisfiable by drupal/core[10.3.1]. - Conclusion: don't install drupal/core 10.3.1 (conflict analysis result) - drupal/core-recommended 10.4.x-dev requires drupal/core 10.4.x-dev -> satisfiable by drupal/core[10.4.x-dev]. - drupal/core-recommended 10.3.x-dev requires drupal/core 10.3.x-dev -> satisfiable by drupal/core[10.3.x-dev]. - You can only install one version of a package, so only one of these can be installed: drupal/core[10.1.0-alpha1, ..., 10.4.x-dev]. - Conclusion: install drupal/core 10.2.x-dev (conflict analysis result) - Root composer.json requires drupal/core-recommended ^10.3 -> satisfiable by drupal/core-recommended[10.3.0-beta1, ..., 10.4.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 - su-sws/stanford_profile 11.x-dev requires drupal/diff ^1.3 -> found drupal/diff[dev-1.x, 1.3.0, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (1.1). - su-sws/stanford_profile[11.0.0, ..., 11.1.0] require drupal/address ^1.2 -> found drupal/address[dev-1.x, 1.2.0, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (^2.0). - su-sws/stanford_profile[11.2.0, ..., 11.3.8] require drupal/core ~10.2.0 -> found drupal/core[10.2.0-alpha1, ..., 10.2.x-dev] but the package is fixed to 10.3.1 (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. - Root composer.json requires su-sws/stanford_profile ^11.0 -> satisfiable by su-sws/stanford_profile[11.0.0, ..., 11.x-dev]. 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 - Root composer.json requires su-sws/stanford_profile ^11.0 -> satisfiable by su-sws/stanford_profile[11.0.0, ..., 11.x-dev]. - drupal/core-recommended 10.3.0-beta1 requires drupal/core 10.3.0-beta1 -> satisfiable by drupal/core[10.3.0-beta1]. - Conclusion: don't install drupal/core 10.3.0-beta1 (conflict analysis result) - drupal/core-recommended 10.3.0-rc1 requires drupal/core 10.3.0-rc1 -> satisfiable by drupal/core[10.3.0-rc1]. - Conclusion: don't install drupal/core 10.3.0-rc1 (conflict analysis result) - drupal/core-recommended 10.3.0 requires drupal/core 10.3.0 -> satisfiable by drupal/core[10.3.0]. - Conclusion: don't install drupal/core 10.3.0 (conflict analysis result) - drupal/core-recommended 10.3.1 requires drupal/core 10.3.1 -> satisfiable by drupal/core[10.3.1]. - Conclusion: don't install drupal/core 10.3.1 (conflict analysis result) - drupal/core-recommended 10.4.x-dev requires drupal/core 10.4.x-dev -> satisfiable by drupal/core[10.4.x-dev]. - drupal/core-recommended 10.3.x-dev requires drupal/core 10.3.x-dev -> satisfiable by drupal/core[10.3.x-dev]. - You can only install one version of a package, so only one of these can be installed: drupal/core[10.1.0-alpha1, ..., 10.4.x-dev]. - Conclusion: install drupal/core 10.2.x-dev (conflict analysis result) - Root composer.json requires drupal/core-recommended ^10.3 -> satisfiable by drupal/core-recommended[10.3.0-beta1, ..., 10.4.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 - su-sws/stanford_profile 11.x-dev requires drupal/diff ^1.3 -> found drupal/diff[dev-1.x, 1.3.0, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (1.1). - su-sws/stanford_profile[11.0.0, ..., 11.1.0] require drupal/address ^1.2 -> found drupal/address[dev-1.x, 1.2.0, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (^2.0). - su-sws/stanford_profile[11.2.0, ..., 11.3.8] require drupal/core ~10.2.0 -> found drupal/core[10.2.0-alpha1, ..., 10.2.x-dev] but the package is fixed to 10.3.1 (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. - Root composer.json requires su-sws/stanford_profile ^11.0 -> satisfiable by su-sws/stanford_profile[11.0.0, ..., 11.x-dev]. 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.