You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I believe satis is no longer working with Composer 2.3:
To Reproduce
Try a satis build with Composer 2.3
Outcome
$ php satis/bin/satis build -vvv satis.json /var/jenkins_home/composer-repo
In BaseCommand.php line 59:
[RuntimeException]
Composer commands can only work with an Composer\Console\Application instance set
Exception trace:
at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/vendor/composer/composer/src/Composer/Command/BaseCommand.php:59
Composer\Command\BaseCommand->getApplication() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/src/Console/Command/BuildCommand.php:183
Composer\Satis\Console\Command\BuildCommand->execute() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/vendor/symfony/console/Command/Command.php:298
Symfony\Component\Console\Command\Command->run() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/vendor/symfony/console/Application.php:1015
Symfony\Component\Console\Application->doRunCommand() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/vendor/symfony/console/Application.php:299
Symfony\Component\Console\Application->doRun() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/src/Console/Application.php:49
Composer\Satis\Console\Application->doRun() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/vendor/symfony/console/Application.php:171
Symfony\Component\Console\Application->run() at /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/satis/bin/satis:60
build [--repository-url REPOSITORY-URL] [--repository-strict] [--no-html-output] [--skip-errors] [--stats] [--minify] [--] [<file> [<output-dir> [<packages>...]]]
Expected behavior
$ php satis/bin/satis build -vvv satis.json /var/jenkins_home/composer-repo
Loading config file /var/jenkins_home/jobs/XXX/jobs/satis-update/workspace/auth.json
Checked CA file /etc/pki/tls/certs/ca-bundle.crt does not exist or it is not a file.
Checked directory /etc/pki/tls/certs/ca-bundle.crt does not exist or it is not a directory.
Checked CA file /etc/ssl/certs/ca-certificates.crt: valid
Executing command (/var/jenkins_home/jobs/XXX/jobs/satis-update/workspace): git branch -a --no-color --no-abbrev -v
Executing command (/var/jenkins_home/jobs/XXX/jobs/satis-update/workspace): git rev-list remotes/origin/master..ab5180af5811f3cd4d23691542f9be02f6556f4c
Executing command (/var/jenkins_home/jobs/XXX/jobs/satis-update/workspace): git describe --exact-match --tags
...
Additional context
Before every satis build we execute a composer update inside our satis directory (the one created by composer create-project composer/satis:dev-main --stability=dev --remove-vcs). Today this updated composer:
I've noticed that there were several releases for the 2.3 branch of composer/composer since then with numerous bugfixes. Can you check if the latest release (2.3.2) still causes issues?
Describe the bug
I believe satis is no longer working with Composer 2.3:
To Reproduce
Try a satis build with Composer 2.3
Outcome
Expected behavior
Additional context
Before every satis build we execute a
composer update
inside our satis directory (the one created bycomposer create-project composer/satis:dev-main --stability=dev --remove-vcs
). Today this updated composer:After that the job failed, as is shown in the outcome section above.
To make it work again I executed the following in the satis directory:
composer req -W 'composer/composer:<2.3.0'
Then the output was again like shown in expected behaviour.
The text was updated successfully, but these errors were encountered: