[BUG] Exception while using in GH action

[mschwemer]

Exception while using in GH action

When using tailor in a gh action, there is an exception.

See https://github.com/in2code-de/powermail/actions/runs/33411757047/job/99552759296#step:8:142

The release some days before the security release everything went fine.

My finding is, that the upload works, but the displayed does not reflect the changes.

https://extensions.typo3.org/extension/powermail

I tried to upload EXT:powermail manually via extensions.typo3.org. This was not possible, because the version number was already in use.

I would be very happy, if this would work again.

Thanks in advance
Marcus

[CybotTM]

Does not look like a tailor issue, seems to be a TER issue.

Except the preg_match warning:

tailor/src/Service/VersionService.php

Line 84 in e8fada1

if (preg_match('/^' . $excludeDirectory . '/i', $path)) {

$excludeDirectory seems not escaped properly.

[CybotTM]

I looked into this. There are two separate defects in that log, and the one causing the failure is not in tailor.

The HTTP 500 comes from TER, and the upload is half-applied

The version record was created by the very request that failed. GET https://extensions.typo3.org/api/v1/extension/powermail/13.3.0 returns a complete record with upload_date 1788192129 = 2026-08-31 16:02:09 UTC, which falls inside the window of the failing job (16:01:54 to 16:02:11), its dependencies are populated, and the archive at https://extensions.typo3.org/extension/download/powermail/13.3.0/zip downloads fine (3.5 MB). What did not happen is the last step: GET https://extensions.typo3.org/api/v1/extension/powermail still reports current_version 13.2.0. That is why the page does not reflect the release and why a manual upload is refused — the number is taken.

Two things worth knowing beyond your report. It is not new with 13.3.0: the three security releases on 2026-08-25 (13.2.1, 12.6.1, 10.9.3) failed identically with Reason: Unknown (Status 500), and the pointer has been stuck since. And it is not a general TER outage — mask 9.0.11 (2026-08-24) and solr 13.1.4 (2026-08-25) published successfully in the same period. The immediate consequence is unpleasant: the extension page currently advertises 13.2.0 as the current version, and 13.2.0 is the one flagged review_state: -1, while 13.2.1 and 13.3.0 exist in the database but are not shown there.

One detail says where the failure sits. Reason: Unknown (HTTP 500) means the response carried neither message nor code; tailor 2.0.0 prints both when TER sends them. TER's RouteHandler catches \Exception, not \Throwable, so a \Error passes it by — no error envelope for the caller, and no entry in the TER.API.REST log either. From the outside the failing statement therefore cannot be narrowed further than "between the version insert and the update of the extension row".

I opened TER!896 for the two halves that are diagnosable from here: make the publish write atomic, so a failure rolls back and a retry is possible instead of the number being burnt, and catch \Throwable so the next occurrence lands in the log with its class, file and line. It does not identify what actually throws — that needs the server-side log for one of these requests.

Until that is sorted out, 13.3.0 cannot be re-uploaded under the same number; someone with TER access has to remove the stored record or fix the pointer.

The preg_match warnings are a tailor bug, but harmless here

VersionService::createZipArchiveFromPath() interpolates each entry of the exclude configuration into a slash-delimited pattern, so your Resources/Private/Build becomes /^Resources/Private/Build/i — PHP reads Private… as modifiers, warns and returns false. The directory is therefore packaged rather than skipped: the published 13.3.0 archive contains 36 files below Resources/Private/Build/, including the Sass sources, gulpfile.js and rollup.config.js. Fix in #106.

This is unrelated to the 500 — the archive was accepted — so please do not close this issue with that PR.

Assisted by claude-code:claude-opus-5 — Session