Review 14.3 Merged

96578[BUGFIX] Resolve composer-named TER dependencies in classic mode

Georg Ringer CR +2 V +2 Easy +35 −2 updated 10/10/26, 05:08

Commit message

When a classic-mode extension declares a dependency in composer.json
using the composer package name (e.g. "friendsoftypo3/content-blocks"),
the Extension Manager failed to auto-fetch it from TER because the
dependency lookup matched only by extension key. The composer package
name data from TER's extensions.xml.gz was already available in
<composerinfo> elements but was ignored.

Parse <composerinfo> from the XML, persist it as a new composer_name
column in the extension table, and extend repository lookups to also
match by composer name.

Review

  • Code review CR +2 Done
    • Georg Ringer +2
  • Verified V +2 Done
    • Georg Ringer +2
    • core-ci +1 CI

Issues 1

Files 2

Review log 34

  1. Georg Ringer commented on patch set 1 10/09/26, 19:33

    Cherry Picked from branch main.
  2. core-ci voted on patch set 1 V +1 10/09/26, 19:45 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/110704

  3. Georg Ringer voted on patch set 1 CR +2 V +2 10/10/26, 05:08

  4. Georg Ringer merged patch set 2 10/10/26, 05:08