fix(supported-version): require RabbitMQ 4.3 for the Magento nightly lane

[marcelmtz]

Problem

With #370 merged, Upstream Nightly in generate-mirror-repo-js gets past Initialize containers for the first time since 2026-05-12 — and immediately hits a second, unrelated failure at setup:install:

Exception: RabbitMQ version "4.1.8" detected. Magento requires RabbitMQ version 4.3.0
or later. Please upgrade RabbitMQ and rerun setup.

In InstallCommand.php line 284:
  [InvalidArgumentException]
  Parameter validation failed

Failing run: https://github.com/mage-os/generate-mirror-repo-js/actions/runs/32290418464/job/96190764643

Magento's development branch has raised its RabbitMQ floor to 4.3.0, but the :next entry still pins rabbitmq:4.1-management, which resolves to 4.1.8.

This was invisible until now: the job never reached setup:install while the MariaDB healthcheck was aborting it at container init.

Fix

One line — magento/project-community-edition:next moves to rabbitmq:4.3-management.

Deliberately scoped to :next only, since that is the entry the nightly kind derives from and the only one tracking the development branch. Released versions keep the RabbitMQ they were verified against, and bumping them would be untested churn against versions that may cap RabbitMQ:

lane	RabbitMQ	changed
@alpha (nightly, from :next)	4.1 → 4.3	✅
2.4.9	4.1	—
2.4.8-p5	4.0	—
2.4.7-p10	3.13	—
Mage-OS nightly	4.1	—

Mage-OS is left alone on purpose: its nightly lane still installs and tests cleanly on 4.1, so its development branch has not taken the upstream change. When it does, mage-os/…:next will need the same bump.

rabbitmq:4.3-management exists on Docker Hub (4.3.5 current), and the floating-minor tag matches the existing convention in these files.

Testing

npm ci && npm test → 122 passed (supported-version) + 18 passed (setup-install).

Since this repo's CI only builds released magento-open-source lanes and never the @alpha nightly lane, I reproduced generate-mirror-repo-js's Upstream Nightly integration check against this branch — resolving supported-version and integration.yaml locally rather than @main, and installing from upstream-nightly.mage-os.org:

https://github.com/marcelmtz/github-actions/actions/runs/32295877753 — green.

"magento":"magento/project-community-edition:@alpha"
"mariadb":"mariadb:11.4"
"rabbitmq":"rabbitmq:4.3-management"

mariadb service is healthy.
Runtime: PHP 8.4.24
OK (1 test, 1 assertion)

That is the full Upstream Nightly path — container init, composer create-project, setup:install, and the integration test — passing end to end.

Also confirmed the released lanes are unaffected: currently-supported still emits 4.1 for 2.4.9, 4.0 for 2.4.8-p5 and 3.13 for 2.4.7-p10, and the Mage-OS nightly lane still emits 4.1.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QLy1odBZniuNwyTAh2AYgL