TYPO3 Forger
  • Dashboard
  • Get involved
  • Reviews
    Overview Ready for review Work in progress Needs action Needs review Needs verification Needs rebase Negative votes Reviewed and verified Ready to merge
  • Issues
    Stale issues Possible duplicates By category By month
  • Sprints
    Overview Initiatives TYPO3 Core Review board
  • Tools
    Backports ReST helper
  • Help
  • Search
  • Login
Esc

Words find the open ones, a number the issue and the change with it.

  1. Issues
  2. #109728
Issue Bug Closed

#109728Make asset:publish during `composer install` more resillient

Helmut Hummel 04/29/26, 10:48 updated 08/11/26, 08:46

Open in Forge Comment in Forge

Description

Since the command is run automatically on composer install
we need to make sure that the composer build process does not
abort, since a failure of this command does not contradict
the composer build, but is rather performed as automation.

Reviews 2

  • 14.3 93906[BUGFIX] Make asset:publish during `composer install` more resilient Resolves this issue Merged Christian Kuhn CR +2 V +2 → main Easy +28 −5 05/02/26, 10:51
  • main 93878[BUGFIX] Make asset:publish during `composer install` more resilient Resolves this issue Merged Helmut Hummel CR +2 V +2 → 14.3 Easy +28 −5 05/02/26, 10:50

Related issues 2

  • Bug #109580Letting out ext:backend as a composer dependency during extension testing fails "asset:publish" Related to Closed composer / dependencies / third-party v14 Markus Klein 04/14/26, 16:51
  • Bug #109716Cannot DI PageRepository in blank projects because constructor calls init which demands DB and other framework context Related to Resolved Code Cleanup v12 Claus Due 04/27/26, 12:13
Author
Helmut Hummel
Priority
Should have
TYPO3 version
14
© 2026 TYPO3 GmbH.
  • API
  • Privacy Policy
  • Legal Notice
  • Feedback