Skip to content

Merge remote-tracking branch 'origin/1.12.x' into 2.0.x #62

Merge remote-tracking branch 'origin/1.12.x' into 2.0.x

Merge remote-tracking branch 'origin/1.12.x' into 2.0.x #62

Triggered via push September 6, 2024 13:34
Status Failure
Total duration 34s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention
Check PHAR checksum
21s
Check PHAR checksum
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Check PHAR checksum
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - phpstan/phpstan-deprecation-rules is locked to version 2.0.x-dev and an update of this package was not requested. - phpstan/phpstan-deprecation-rules 2.0.x-dev requires phpstan/phpstan ^2.0 -> could not be found in any version, there may be a typo in the package name. Problem 2 - phpstan/phpstan-nette is locked to version 2.0.x-dev and an update of this package was not requested. - phpstan/phpstan-nette 2.0.x-dev requires phpstan/phpstan ^2.0 -> could not be found in any version, there may be a typo in the package name. Problem 3 - phpstan/phpstan-phpunit is locked to version 2.0.x-dev and an update of this package was not requested. - phpstan/phpstan-phpunit 2.0.x-dev requires phpstan/phpstan ^2.0 -> could not be found in any version, there may be a typo in the package name. Problem 4 - phpstan/phpstan-strict-rules is locked to version 2.0.x-dev and an update of this package was not requested. - phpstan/phpstan-strict-rules 2.0.x-dev requires phpstan/phpstan ^2.0 -> could not be found in any version, there may be a typo in the package name. Potential causes: - A typo in the package name - The package is not available in a stable-enough version according to your minimum-stability setting see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details. - It's a private package and you forgot to add a custom repository to find it Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
Check PHAR checksum
Process completed with exit code 2.