[TASK] Add proper replaces for merged core extensions
If we merge a core extension into another one, it means that the remaining extension technically replaces the removed one. To ease upgrades for composer based installations, we now declare these replacements properly. Resolves: #85250 Related: #81225 Related: #81787 Related: #81768 Related: #82896 Related: #82505 Related: #84680 Related: #81735 Related: #83631 Releases: master Change-Id: I977a008de8b13fe61b5a7c091ad8d12cd45f6e4d Reviewed-on: https://review.typo3.org/57208 Reviewed-by:Mathias Brodala <mbrodala@pagemachine.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Helmut Hummel <typo3@helhum.io>
Showing
- composer.json 2 additions, 5 deletionscomposer.json
- composer.lock 1 addition, 1 deletioncomposer.lock
- typo3/sysext/backend/composer.json 5 additions, 1 deletiontypo3/sysext/backend/composer.json
- typo3/sysext/core/composer.json 3 additions, 1 deletiontypo3/sysext/core/composer.json
- typo3/sysext/documentation/composer.json 0 additions, 1 deletiontypo3/sysext/documentation/composer.json
- typo3/sysext/info/composer.json 2 additions, 1 deletiontypo3/sysext/info/composer.json
- typo3/sysext/workspaces/composer.json 2 additions, 1 deletiontypo3/sysext/workspaces/composer.json
Please register or sign in to comment