The `E_STRICT` constant is deprecated as of PHP 8.4 and will be removed in PHP 9.0 (commit finally went in today).
The error level hasn't been in use since PHP 8.0 anyway and was only barely still used in PHP 7.x, so removing the exclusion from the `error_reporting()` setting in these script shouldn't really make any difference in practice.
Ref:
* https://wiki.php.net/rfc/deprecations_php_8_4#remove_e_strict_error_level_and_deprecate_e_strict_constant
Co-authored-by: jrfnl <jrfnl@users.noreply.github.com>
* Add option to run bump after update
* Convert the option into a bool | string parameter and change a couple of texts
* Apply suggestions from code review
* Fix tests
---------
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
* Add allow-missing-requirements configuration to ignore error during install if there are any missing requirements
* Add test for allow-missing-requirements config
---------
Co-authored-by: Joe <joe@wpj.cz>
* Improve interactive package updates
* Exclude platform packages and up to date packages, follow stability flags, ignore-platform-reqs etc
* Add tests and support for lock file + empty lock/vendor
---------
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
* Add `--abandoned` option
* Refactoring
- Use `Auditor::ABANDONEDS` in `Config.php`
- Drop `getAuditAbandoned()` from `BaseCommand.php`
* Modify cli docs
* Add single test case for interactive `init` command
* Fix spelling + use single quotes
* Fix test expectations
---------
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
* Add `GlobalCommandTest.php`
- `testGlobal` to check `COMPOSER_HOME` is followed correctly + check
`COMPOSER` is unset.
- `testNotCreateHome` to test handling invalid `COMPOSER_HOME`.
* Add error string for non obvious test case
* Clean up env vars and minor code style changes
---------
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
* Add test case for conflicting both with `--dev` and without
* Implement interactive case
* Restrcture so that interactive case is actually interactive
I don't know why specifying `'--no-interaction' => !$isInteractive,`
didn't give the desired behavior of the prompt being interactive.
You can verify that by printing the `$appTester->getDisplay()` which
doesn't contain a prompt. In fact, it doesn't make any difference
whether I set it to true or false. The only difference is if I set it
or don't set it.
* Fix dreaded trainling comma
Jordi Boggiano