The Mercure job follows dunglas/mercure:latest and breaks on every pull request
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start in .github/workflows/ci.yml, where the PHPUnit (PHP 8.5) (Mercure) job declares the dunglas/mercure service image. Review the failing ApiPlatform\Tests\Test\ApiTestCaseTest::testGetMercureMessages test and the recorded image digests, then confirm the Mercure tag with a maintainer. Done means pull requests no longer follow an unpinned latest image and the Mercure test passes.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- PHP
- Stars
- 2.6k
- Forks
- 982
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 45
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from api-platform/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
api-platform/core#8495 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
api-platform/core#8471 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
api-platform/core#8475 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
api-platform/core#8447 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
api-platform/core#8312 · 2 comments ·
All issues in api-platform/core
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
status/awaiting_triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Issue: ready for confirmation Reported on 2.4.x
Difficulty 2/5 1-3 hours Newbie friendliness 88/100