TYPO3 Core

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85212

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85212

Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85198

Just want to mention that this also affected TypoScript loaded from v13 site-sets, because packagePath ended up as "/var/www/html///":

object(TYPO3\CMS\Core\Package\Package)#294 (8) {
  ["partOfFactoryDefault":protected]=>
  bool(false)
  ["partOfMinimalUsableSystem":protected]=>
  bool(false)
  ["serviceProvider":protected]=>
  uninitialized(?string)
  ["packageKey":protected]=>
  string(15) "theme_portfolio" 
  ["packagePath":protected]=>
  string(16) "/var/www/html///" 

…which then got ignored by the TypoScript parser once it was composed into "/var/www/html///Configuration/Sets/ThemePortfolio"

Good news is: The (already merged) patch solves this case as well :)