* 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 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
* Fix: Add test case for not dropping patch version for tilde
* Fix some edge cases of tilde constraints in bump command, fixes#11218
---------
Co-authored-by: Matthias Vogel <git@kanti.de>
Composer has always allowed a single http_proxy (or CGI_HTTP_PROXY)
environment variable to be used for both HTTP and HTTPS requests. But
many other tools and libraries require scheme-specific values.
The landscape is already complicated by the use of and need for upper
and lower case values, so to bring matters inline with current practice
https_proxy is now required for HTTPS requests.
The new proxy handler incorporates a transition mechanism, which allows
http_proxy to be used for all requests when https_proxy is not set and
provides a `needsTransitionWarning` method for the main application.
Moving to scheme-specific environment variables means that a user may
set a single proxy for either HTTP or HTTPS requests. To accomodate this
situation during the transition period, an https_proxy value can be set
to an empty string which will prevent http_proxy being used for HTTPS
requests.
We now update the existing package instead of reverting changes in the updated package to ensure we keep all metadata intact, fixes#11787
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
Jordi Boggiano