The PHPUnit (PHP 8.5) (Mercure) job fails on every pull request since some point between 2026-09-16 and today, on the same test:
1) ApiPlatform\Tests\Test\ApiTestCaseTest::testGetMercureMessages
{"detail":"Failed to send an update.","status":500}
It comes from the hub image, not from the pull requests
.github/workflows/ci.yml declares the service as image: dunglas/mercure, so the tag is latest and the runner pulls whatever is current:
|
image digest |
result |
main, 2026-09-16 |
sha256:916834e4… |
green |
| #8479, today |
sha256:33223c37… |
fails |
| #8548, today, not mine |
sha256:33223c37… |
fails, same test |
Both of today's runs log Status: Downloaded newer image for dunglas/mercure:latest. A pull request that touches nothing related to Mercure fails exactly like one that does, which points at the image rather than at the changes.
I have not worked out what the new image changed, only that the job follows the digest. MERCURE_EXTRA_DIRECTIVES and the JWT keys in the workflow are the kind of configuration a hub release can tighten.
Suggestion
Pinning the service to a released tag, dunglas/mercure:v0.19 or whichever line you track, would keep a hub release from turning every pull request red, and would make the upgrade a deliberate commit you can review on its own.
Happy to send that pull request if you tell me which tag you want to sit on. I would rather not pick the version for you.
The
PHPUnit (PHP 8.5) (Mercure)job fails on every pull request since some point between 2026-09-16 and today, on the same test:It comes from the hub image, not from the pull requests
.github/workflows/ci.ymldeclares the service asimage: dunglas/mercure, so the tag islatestand the runner pulls whatever is current:main, 2026-09-16sha256:916834e4…sha256:33223c37…sha256:33223c37…Both of today's runs log
Status: Downloaded newer image for dunglas/mercure:latest. A pull request that touches nothing related to Mercure fails exactly like one that does, which points at the image rather than at the changes.I have not worked out what the new image changed, only that the job follows the digest.
MERCURE_EXTRA_DIRECTIVESand the JWT keys in the workflow are the kind of configuration a hub release can tighten.Suggestion
Pinning the service to a released tag,
dunglas/mercure:v0.19or whichever line you track, would keep a hub release from turning every pull request red, and would make the upgrade a deliberate commit you can review on its own.Happy to send that pull request if you tell me which tag you want to sit on. I would rather not pick the version for you.