Update dependency composer/composer to v2 #169
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/composer-composer-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.10.24
->2.2.3
Release Notes
composer/composer
v2.2.3
Compare Source
v2.2.2
Compare Source
COMPOSER_BIN_DIR
env var and_composer_bin_dir
global containing the path to the bin-dir for binaries. Packages relying on finding the bin dir with$BASH_SOURCES[0]
will need to update their binaries (#10402)v2.2.1
Compare Source
v2.2.0
Compare Source
dev-main
as the default path repo package version if no VCS info is available (#10372)v2.1.14
Compare Source
v2.1.12
Compare Source
9999999
-dev being shown in some cases by theshow
command (#10260)v2.1.11
Compare Source
v2.1.10
Compare Source
require
command reverting changes even though dependency resolution succeeded when something fails in scripts for example (#10118)require
not finding the right package version when some newly required extension is missing from the system (#10167)e1dbd65
)v2.1.9
Compare Source
show --all foo/bar
which as of 2.0.0 was not showing all versions anymore but only the installed one (#10095)v2.1.8
Compare Source
v2.1.7
Compare Source
v2.1.6
Compare Source
ircs://
protocol for support.irc composer.json entriesv2.1.5
Compare Source
create-project
creating aphp:
directory in the directory it was executed in (#10020, #10021)v2.1.4
Compare Source
only
/exclude
properties to avoid matching names as sub-strings of full package names (#10001)archive
command not working with async archive extractioninit
command being able to generate an invalid composer.json (#9986)v2.1.3
Compare Source
dump-autoload
command not dispatching scripts anymore, regressed in 2.1.2 (#9954)v2.1.2
Compare Source
--dev
todump-autoload
command to allow force-dumping dev autoload rules even if dev requirements are not present (#9946)--no-scripts
disabling events for plugins too instead of only disabling script handlers, using--no-plugins
is the way to disable plugins (#9942)v2.1.1
Compare Source
v2.1.0
Compare Source
v2.0.14
Compare Source
v2.0.13
Compare Source
update --lock
listing updates which were not really happening (#9812)v2.0.12
Compare Source
v2.0.11
Compare Source
v2.0.10
Compare Source
symfony/flex
make sure you upgrade it to 1.12.2+ to fixdump-env
issues)exec
command suppressing output in some circumstancespath/to/foo
, which are now rewritten internally topath\to\foo
when needed@php vendor/bin/foo
to work cross-platform9999999
-dev internally. This alias now only applies to default branches being non-numeric (e.g.dev-main
)v2.0.9
Compare Source
archive
and path repo copies mishandling some .gitignore pathsconfig
orrequire
modifies large composer.json filesv2.0.8
Compare Source
git gc
applied to them periodicallyv2.0.7
Compare Source
remove
command requiring a lock file to be presentComposer\InstalledVersions
to always contain up to date data during installationstatus
command breaking on slow networksv2.0.6
Compare Source
v2.0.5
Compare Source
php-only
), set platform-check totrue
if you want a complete checkv2.0.4
Compare Source
check-platform-req
command not being clear on what packages are checked, and added a --lock flag to explicitly check the locked packagesconfig
&create-project
adding of repositories to make sure they are prepended as order is much more important in Composer 2, also added a --append flag toconfig
to restore the old behavior in the unlikely case this is neededv2.0.3
Compare Source
outdated
command where dev packages with branch-aliases where always shown as being outdateddev-master as xxx
aliases--locked
option being missing fromoutdated
command, for checking outdated packages directly from the lock filev2.0.2
Compare Source
composer show -s
in projects where no version can be guessed from VCSrequire
when a lock file was missingv2.0.1
Compare Source
v2.0.0
Compare Source
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Update dependency composer/composer to v2.2.0to Update dependency composer/composer to v2.2.1c1c121c195
to9e4185ee4c
Update dependency composer/composer to v2.2.1to Update dependency composer/composer to v2.2.29e4185ee4c
to5f15f77c48
Update dependency composer/composer to v2.2.2to Update dependency composer/composer to v2.2.35f15f77c48
to8fbcfbf133
Update dependency composer/composer to v2.2.3to Update dependency composer/composer to v28fbcfbf133
to47cdadf94a
Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 2.x releases. However, if you upgrade to 2.x manually then Renovate will reenable minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.
Pull request closed