- Aug 13, 2024
-
-
Oliver Hader authored
Change-Id: I75549bf18ee2714a478d832a72b8a79d01fc9f61 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85606 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
- Jul 09, 2024
-
-
Oliver Hader authored
Change-Id: I72e06646233894cfbd8017bef8a5620e17caf32a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85174 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
-
Oliver Hader authored
Change-Id: I20500c48221bf14b56baef7551a423571883c6a9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85173 Reviewed-by:
-
- Jun 11, 2024
-
-
Oliver Hader authored
Change-Id: I86360df1a2a39b3fb1ebca927fe2a714bc887691 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84600 Tested-by:
-
Oliver Hader authored
Change-Id: If61da3b4e4166c368989faab63ae87c26330e588 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84599 Tested-by:
-
- May 14, 2024
-
-
Oliver Hader authored
Change-Id: I38c57b5342892945c8b91bb72570faa9b5a28665 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84271 Tested-by:
-
Oliver Hader authored
Change-Id: Iedbda8b0217bab62bb7647a7c962f564faaf003e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84270 Tested-by:
-
- Apr 09, 2024
-
-
Benni Mack authored
Change-Id: I0e897680df27e5380344f4436a7db7a6085d0688 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83717 Reviewed-by:
-
Benni Mack authored
Change-Id: Ibd990830d7ad9d43707be802c6a24a1388589d18 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83716 Tested-by:
-
- Mar 19, 2024
-
-
Benni Mack authored
Change-Id: I03729854c268a32ba072d891d4701d42ba5d365d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83517 Tested-by:
-
Benni Mack authored
Change-Id: I981c2fe620a96ce344730b184ce60e7aa17a6aa4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83516 Reviewed-by:
-
Benjamin Franzke authored
All applicable acceptance tests are now also executed in composer mode. Tests that check classic-mode specific functions are excluded and are therefore now tagged as classic-mode test. The composer mode instance is generated with our CLI setup tools, allowing to mimic the realworld case where a instance is creating via our setup tools instead of from fixtures (which we still use for classic mode tests, but try to reducde/avoid for composer mode tests). The existing existing classic-mode test acceptance test execution will keep running as-is. The v12 backport additionally imports pieces from #102440 as t3editor extension is enabled in this composer-mode, while v12 classic mode is tested (for historic reasons) without t3editor extension enabled. Commands executed: > composer require --dev "typo3/cms-styleguide":"^12.0.5" Resolves: #103297 Releases: main, 12.4, 11.5 Change-Id: I64973f110931b51ed2ef7ef8f8cc3411834fcf37 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83263 Reviewed-by:
Benjamin Franzke <ben@bnf.dev> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
- Oct 03, 2023
-
-
Simon Schaufelberger authored
In order to test local composer packages, they need to be placed under the "packages" directory in "Build/composer". To autoload these packages automatically, the necessary setup is adjusted. Resolves: #102054 Releases: main, 12.4 Change-Id: I6c40a06142efaf13493a149efc636da9837c3598 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/81315 Tested-by:
-
- Mar 28, 2023
-
-
Benni Mack authored
Change-Id: I890274b2574c6af78b9406df0f89557ba7998425 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78293 Tested-by:
-
- Feb 07, 2023
-
-
Benni Mack authored
Change-Id: Ie632b791d59866eddbe3e22f654fb261b7e02f6b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/77747 Tested-by:
-
- Dec 06, 2022
-
-
Benni Mack authored
Change-Id: I206be78ca4e53366c8ded19ebbabdf6ec4047471 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76935 Tested-by:
-
- Oct 04, 2022
-
-
Oliver Hader authored
Change-Id: I1feb236aeae9b3b7da1c50d5f65daf4fca4727bc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75974 Tested-by:
-
- Sep 28, 2022
-
-
Christian Kuhn authored
Extension 'recordlist' is a must-have extension that is part of 'minimal usable system' and always loaded: Especially 'backend' has various cross dependencies to 'recordlist', backend "search" using the list module for detail display is one of the most obvious ones. In general it's bad if the main 'backend' extension has such direct dependency towards another more specific extension: The core development slowly strives to have the tuple 'core-backend-frontend' as main set of crucial extenions, with eventually making 'backend' and 'frontend' optional in some happy future. To solve the unfortunate dependency from 'backend' to 'recordlist', 'recordlist' is now merged into 'backend', reducing the set of extensions required for a 'minimal usable system' by one. > composer update --lock Change-Id: Ie73ccb992b9ad29626478ff9acd6dc9a15b8aa9a Resolves: #98443 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75876 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
- Jan 17, 2022
-
-
Stefan Bürk authored
With composer >=2.2.0, allowed composer plugins have to be added to composer.json as config/allowed_plugins. This has been prepared with #96428 for core root composer.json. The patch missed according changes for test related distribution Build/composer/composer.dist.json. Resolves: #96555 Related: #96428 Releases: main, 11.5 Change-Id: I7cc8c8a819969632fd85db33637ae652a3138748 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73038 Tested-by:
-
- Dec 03, 2021
-
-
Helmut Hummel authored
Add versions to repo instead of exposing the root version as env var, when composer installing on CI. This has the benefit, that these versions can be automatically changed by darth (https://github.com/TYPO3/darth/pull/18/commits/083016b43a6ab5860b5a680cbab7d25a890ea0b6) and that all installs, even the ones where the env vars are not exposed, use consistent versions. Releases: main Resolves: #96102 Change-Id: Ic0f3d77fe21f47b1d3b09041800018885bfb4409 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72406 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
-
- Nov 30, 2021
-
-
Helmut Hummel authored
Since branching is finished, the dev-master alias is obsolete and can be removed. Used composer command: > composer up --lock Releases: main Resolves: #96102 Change-Id: I3ef3f546bb705b2fda4040b6cb8092b46bde76a9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72379 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
-
- Sep 11, 2021
-
-
Christian Kuhn authored
We're delivering a "test distribution" composer.json in Build/composer since #94996. The patch adds "runTests.sh -s composerTestDistribution" that "composer update" this project and adds it to pre-merge and nightly integrity suite. This verifies core dependencies are fine at all times. Main difference to the monorepo: This composer setup has no dev dependencies that influence version decisions. Resolves: #95188 Related: #94996 Releases: master Change-Id: I04084a2a44a69903d523b5c4740d62d7dc46c1f1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71030 Tested-by:
-
- Aug 27, 2021
-
-
Helmut Hummel authored
The idea of this change is, that when using Composer, all TYPO3 extensions, that are part of the Composer installation, should be considered as active and there is no need whatsoever to install code of an extension with Composer (and making all its classes available), but not wanting the extension to interact with TYPO3 API. Therefore with this change, all TYPO3 extensions installed with Composer are considered to be active (and therefore can and will interact with TYPO3 API). Additionally, since the list of active extension is known during Composer installation, a persistent artefact is created at this point, which represents the final state of TYPO3 extension packages for the PackageManager, making both, the PackageStates.php file and the PackageManager cache obsolete for Composer managed TYPO3 installations. Note any extension present in the typo3conf/ext folder, but not installed by Composer, will still be considered and marked as part of TYPO3 packages when doing a "composer install". The only requirement here is, that such extensions need a composer.json file nonetheless. Note this behaviour is deprecated and will be removed with TYPO3 12. Additionally the extension manager UI is adapted to not allow changing the active state of extensions anymore. Respectively the commands "extension:activate" and "extension:deactivate" are disabled in Composer managed systems as well. A new cli command "extension:setup" is introduced, which supersedes both, the extension manager UI as well as the activate/deactivate commands. It performs all steps that were done before, except changing the active state of an extension. With cli command "extension:setup" ALL extensions are set up in terms of database schema changes, static data import, distribution files imports, etc. Last but not least, any installed Composer package, that defines an extra.typo3/cms section in their composer.json file, but is not of type "typo3-cms-extension" at the same time, will be considered for TYPO3 and will have full access to TYPO3 API. It has to be noted though that such packages can not deliver public resources. This remains exclusive for TYPO3 extensions for now. Releases: master Resolves: #94996 Change-Id: I919873dd4ddd087c943f1289a12253c6acec7fa4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69174 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
